OneSpan Sign Release Notes

SaaS 2024-October: Release 24.R5.3 (11.59.3)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on October 28, 2024.

Bug Fixes

• We fixed an issue that occurred when a signer attempted to sign a multiple signature blocks transaction with QES SwissComm. (refs PB-110257)
• In certain situations the Signer Experience would not load until you resized the browser. This no longer happens. (refs PB-110518)

SaaS 2024-October: Release 24.R5.2 (11.59.2)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on October 8, 2024.

Bug Fixes

• We have fixed an ssl connection issue that resulted in a failure to retrieve an oAuth2 access token from the authorization server. (refs PB-109939)

SaaS 2024-September: Release 24.R5.1 (11.59.1)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on September 30 , 2024.

Bug Fixes

General

• Attempting to retrieve an audit trail and its relevant documents using a GET /api/packages/PACKAGE_ID/audit call with a Manager's API would sometimes fail, with an error message stating that the user did not have the proper access. This no longer occurs. (refs MAIN-9476)
• In some environments not all documents in a transaction would be returned to their Box folder when using OneSpan Sign Embedded Integration for Box . This has been fixed. (refs PB-109772)

EKS Environments

• To address an issue where '500 errors' would sometimes occur when creating a transaction using multipart POST requests, we have improved our error handling so that unknown MIME encodings are now ignored. (refs PB-109875)

• We have simplified our application tooling to prevent connectivity errors to remote resources. This would sometime occurs when using OAuth2 with connectors such as Dynamics CRM. (refs PB-109789)

SaaS 2024-September: Release 24.R5 (11.59)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on September 26, 2024.

What's New

Here are some of the new features and enhancements we have made for this release.

Design Change Advisory - ADA Compliant Designer

The Designer page has been improved for a cleaner user experience and to meet ADA requirements: (refs PB-99115)

• We have revised the color palette of recipient fields to meet WCAG 2.0 compliance standards. We have enhanced the readability of the text within those fields by using lighter colors to increase the contrast between the text and its background.

• Fields now display the default value for the field, instead of the field type. In addition, the Signature and Initials fields now display only the signature type, so as to emphasize the action the signer should take. This is to give Senders a better idea of the text alignment of the Sign button text that recipients will see in the Signing ceremony.

• Our field icons have been updated.
• The field settings panel now displays the field type, and has been updated with the new icons.

Admins

• Ability to limit languages: Administrators can now limit the languages that can be used for signing transactions. With this feature you can now define the a list of supported languages that can be used during the New Signer Experience, as well as specify a default language for signing. This allows you to control the branding and white labeling of your transactions. (refs PB-102382)

• Improved performance and logging of callback failures: We’ve improved logging to make it easier to trace callback failures. We have also made some technical improvements that will lead to better performance. (refs PB-105747)

• Enhanced System Updates Log Reports are now available: You can now use our APIs to retrieve logs related to account configuration events. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-106227)

  • Feature setting updates

  • Transaction setting updates

  • Security setting updates
• A New Delegation Log Report is now available: You can now use our APIs to retrieve logs related to delegation events. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-106419)

  • Delegation creation

  • Delegation editing

  • Delegation deletion

Evidence Summary

• New verification error messages: There is now a new error message that appears when authentication fails due to an unsupported document, or a document that failed to process. (refs PB-100036)

• The verification results tables can now be sorted alphabetically: The Matcher column in the verification results table can now be sorted alphabetically, to make it easier to find the information you are looking for. (refs PB-102952)

Integration Platform

• New workflow integrations: We have added new integrations to connect eSignatures to your favorite business applications. The following new integrations have been added (refs PB-105335):

  • OneDrive

  • Dropbox

Notarization

• We have switched audio-video providers: Beginning with this release we will be using Vonage as our audio-video provider, instead of Twilio. (refs PB-104371)

• Florida and Indiana now support Remote Online Notarization: Using the RON is now legally accepted in the states of Florida and Indiana. (refs PB-105903)

• Notary training videos now included in invitation email: Once your account has been updated to enable RON and IPEN transactions you will receive an onboarding email that now includes a link that quickly requests access to our Online Learning Academy and our Notary videos. (refs PB-106864)

Senders

• There is now a simpler way to change a recipient's type: Changing a recipient's type can now be done directly in the Designer, without having to move back to the transaction page. This allows you to easily make recipient type changes, such as replacing placeholders before sending the transaction before signing. (refs PB-106694)

Signers

• New Authentication Sign-in page: Signers that have an associated authentication method are presented with an introduction page on accessing the signing ceremony, informing them that they will need to authenticate before continuing. This page is now displayed by default for esigning and in-person transactions where the authentication method is set to any of the following: Q&A, SMS, Q&A+SMS, or KBA. Note that this page cannot be disabled as it allows signers to explicitly consent to the authentication process and it prevents virus scans and preview applications from triggering unwanted authentication requests from a recipient's email inbox. (refs PB-106194)

Bug Fixes

The following issues were resolved in this release:

Admins

• When searching for a sender's template using an API call a 403 error would sometimes appear. This happened when searching for the template using the sender's email. Searching for a template using a sender's email was case-sensitive, meaning that if an improper case was used in the search parameters the template would not be found. We have fixed this so that this specific search is no longer case-sensitive. (refs PB-107800)

Evidence Summary

• We have fixed an issue where the wrong IP address would show when completing an IDV journey. (refs PB-106780)

• If a signer accessed the Signer Experience from two different countries the evidence summary would report only one IP address. This has been fixed so that the evidence summary now shows both IP addresses. (refs PB-107644)

Senders

• Attempting to copy, paste, and move the same field created performance issues and errors. This has been fixed. (refs PB-106784)

• Transaction with mandatory attachments cannot be set to autocomplete. However, it was possible to edit a transaction via API and set autocomplete to true, even if there were mandatory attachments in the transaction. This made it possible to complete a transaction before the mandatory attachment had been uploaded. This has been fixed and is no longer possible. (refs PB-108170)

Signer Experience

• When editing a transaction by adding or removing documents, signers would sometimes be redirected to a document that was not next in the signing order. This document would not have any signature fields for them to sign. This no longer happens. (refs PB-107200)

Upcoming Changes

Here are some of the new features, changes and enhancements that we will be introducing in an upcoming release.

• In an upcoming release, some validation will be added to the Signer phone number input (via PUT and POST API calls) and to the Sender phone number input (under My Account > Personal Information). The following changes will be made (refs PB-104448):

  • Input will be restricted to a maximum length of 15 characters

  • Alphanumeric characters will be allowed

  • The following special characters will be allowed: + - # ( )

SaaS 2024-July: Release 24.R4 (11.58)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on September 19, 2024.

What's New

Here are some of the new features and enhancements we have made for this release.

Admins

• Administrators can now allow signers to download evidence summaries: Using the Account Configuration page administrators can now configure their accounts so that signers can download evidence summaries. Previously, to enable this feature you had to contact our Support Team. (refs PB-104692)

  Evidence summary documents contain Personally Identifiable Information (PII). Enabling this feature should be done with caution.

• New events available in the Event Notifications page: To address an issue that was causing certain events to be reset when updating the list of events, the following existing events have now been exposed in the Event Notifications page: (refs PB-105022)

  • eOriginal deposit succeeded

  • eOriginal deposit attempt failed

  • eOriginal deposit failed

  • Video recording failed

• System Access Reports are now available: You can now use our APIs to retrieve logs related to system access events. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-105334)
  • User logins, logouts, or login failures
  • The start and end of a recipient delegation
  • SSO logins
• Improved Subscription Page: The Subscription page now includes additional headers that help improve the clarity and readability of your subscription plan. (refs PB-105403)
• Enhanced User Management Report: We have added Group Management Events to the User Management Report (available through our Interactive API Reference. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-105621)
  • The addition or deletion of a Group Member.

Authentication

• Added multi-factor authentication type: Once enabled recipient authentication can be done using both questions and answers, and SMS codes. Once a recipient passes the question and answer they will then have to also authenticate themselves with an SMS code. This added level of authentication provides additional security for your recipient authentication. (refs PB-104537)

• New SMS message templates for China, Hong Kong, and Vietnam: In accordance with local requirements the SMS messages used for authentication in China, Hong Kong, and Vietnam will now use the locally required language, regardless of the language used by the Recipient. (refs PB-105986)

• Increased character length for Vonage brand name: When using Vonage as a service provider for OTP, the number of characters that can be used in the brand name has been increased to 32.

Evidence Summary

• External links are now tracked: Clicking on external links during the New Signer Experience is now tracked in the Evidence Summary. In addition, the document name with the external link and the URL of the external link are also tracked. The following events have been added to the Evidence Summary: (refs PB-103660)

  • Click external link

  • Decline external link

  • Confirm external link.

Notarization & Virtual Room

• RON recordings can now be retrieved even after a transaction or account has been deleted: Recordings of RON sessions can now be retrieved from a deleted transaction, or even a deleted account. To retrieve one of these sessions, contact our Support Team. (refs PB-104394)

Senders

• Increased the width of the color bar associated to a recipient within the Designer page: For an improved sender experience we have increased the width of the color in the recipient list. This makes it easier to quickly differentiate between recipients. (refs PB-101777)

• Senders can now allow signers to download evidence summaries: If enabled by their administrators Senders can now configure their transactions so that specified signers can download evidence summaries. (refs PB-105109)

  Evidence summary documents contain Personally Identifiable Information (PII). Enabling this feature should be done with caution.

Virtual Room

• Improved co-browsing screen loading time: We have improved the performance of the Virtual Room when screen sharing.

Bug Fixes

The following issues were resolved in this release:

Admins

• Our Transaction reports now properly display the number of attachments that have been uploaded. (refs PB-101740)

API Calls

• Using a GET/api/account/senders/sender-id call would sometimes result in a 403 error. This issue has been fixed. (refs PB-105031)

• Fixed an error in our Open API documentation that listed attachment information as being available in the GET/api/reports/transaction-summary call. (refs PB-105422)

Authentication

• The grant type for event notifications with oAuth 2.0 authentication was not set correctly when configuring using the Event Notifications page. This now works as expected. (refs PB-105028)

• The access token used to send a callback could be retrieved as XML, and not JSON. This error no longer occurs. (refs PB-105642)

OneSpan Sign Embedded Integration for Box

• In certain environments attempting to create a transaction resulted in a 'null' error. To address this issue we have created two new OneSpan Sign Embedded Integration for Box connectors. They can be downloaded from the following links (refs MAIN-9302):

  • For FedRAMP Production environments: https://app.box.com/app-center/onespan_sign_gov/app/gEpTuxu5uP

  • For Canadian Production environments: https://app.box.com/app-center/onespan_sign_ca/app/ni9ioyE4Wi

Evidence Summary

• Signer handoff information is correctly captured in the Evidence Summary for iPEN transactions. (refs PB-104004)

Senders

• When using a slow internet connection, moving a field in the Designer sometimes lead to 405 errors and screen freezes, especially if you tried to move the field multiple times. This has been fixed. (refs PB-91868)

• Senders can no longer create and send transactions using a canceled account. (refs PB-104840)

• In some environments Senders could not zoom out on a document in the Designer. This has been resolved. (refs PB-105002)

Signer Experience

• Closing the Exit Signing Mode prompt with the Don't show this message again checkbox selected using the 'X' button would cause this prompt to not show again. The expected behavior is that clicking the 'X' button would cancel the action. Instead, the New Signer Experience would act as if the OK button was clicked, and the prompt would no longer appear. Clicking 'X' to cancel this action now works as expected, with the Exit Signing Mode prompt appearing again. (refs PB-91868)

• Previously, if a transaction was deleted after a signer had completed a transaction but before they had closed the Thank You page, clicking the Download Documents button resulted in nothing happening. Now, an error message appears informing the signer that the transaction is no longer available. (refs PB-95286)

• Signers would sometimes have to refresh their browser to see signatures fields on a signed document. This occurred when accessing these documents using the Review Documents button. (refs PB-105680)

• We've resolved a problem where, after attempting to decline a transaction with a reason that used characters that could be perceived as security vulnerabilities, the signing page did not refresh properly. Instead, the signer was presented with a Transaction Declined page, when the transaction itself was still in a Sent state. Now, everything works as expected, and the page updates correctly. (refs PB-105729)

Changed Behavior

Here are some of the changes in behavior that you might want to be aware of.

• The Recipient Authentication tab has been updated to provide a cleaner, more user-friendly user experience. Radio buttons have been replaced with drop-down lists, and unnecessary text has been removed. (refs PB-104541)

Upcoming Changes

Here are some of the new features, changes and enhancements that we will be introducing in an upcoming release.

• The Designer page is getting a facelift! Look for the following enhancements in a future release: (refs PB-99115)

  • ADA friendly colors

  • Default values displayed in fields

  • Updated field icons

  • A cleaner user experience

• Upcoming breaking change in input parameter for OAuth2/token API request: (refs PB-105508)

  SDK users:

  • Need to upgrade to SDK version 11.58 before our next release 24.R5

  For API integrators:

  • We support 'grant_type' query parameter and form parameter until release 24.R4
  • Starting from release 24.R5, 'grant_type' can be only provided as form parameter

SaaS 2024-July: Release 24.R3.5 (11.57.5)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on July 19, 2024.

Bug Fixes

• You will no longer receive an Access Denied error message when accessing the Thank you summary page using authentication tokens. This sometimes occurred during in-person transactions. (refs PB-107560)

Vulnerabilities

• Applied a security patch.

SaaS 2024-July: Release 24.R3.4 (11.57.4)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on July 11, 2024.

Bug Fixes

• Fixed an issue where certain inflight transactions created in 11.57.2 were not able to be completed in 11.57.3 (refs PB-107249)

Vulnerabilities

• Applied a security patch.

SaaS 2024-July: Release 24.R3.3 (11.57.3)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on July 3, 2024.

Bug Fixes

• Downloading signed documents sometimes resulted in fields not being visible. This occurred when fields had the same values. This has been fixed. (refs PB-107022)

SaaS 2024-June: Release 24.R3.2 (11.57.2)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on June 22, 2024.

Bug Fixes

• The Signer Experience now loads properly after a successful user authentication. Previously, attempting to access the Signer Experience more than once would cause the system to freeze. This issue occurred on Android devices using in-app browsers, such as WebView, and with customized event configurations. (refs PB-106853)

SaaS 2024-June: Release 24.R3.1 (11.57.1)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on June 18, 2024.

Bug Fixes

• Fixed an issue where the documents for transactions were not vaulted for Sandbox accounts that use lending or mortgage workflows. (refs MAIN-9042)
• Fixed an issue with displaying Helvetica fonts with custom encoding. The custom encoding is now mapped internally. (refs PB-103575)
• Fixed an issue where the ZapfDingbats font was not listed in the Designer and was not displayed during signing. (refs PB-104975)

SaaS 2024-May: Release 24.R3 (11.57)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on June 18, 2024.

What's New

Here are some of the new features and enhancements we have made for this release.

OneSpan Integration Platform

We are introducing the OneSpan Integration Platform, which allows you to use a single solution to connect eSignatures to your favorite business applications in an easy, secure, and cost-efficient way.

OneSpan Integration Platform can deliver eSignature integration with multiple applications, such as Google Workspace, Salesforce, and Workday. In the future this platform will also support a self-serve marketplace as well as BYOI (Bring your own iPaaS [Integrations-platform-as-a-service]).

For more information, please contact our Sales Team or your Customer Success Manager.

Accessibility

• The Manage Delegation page is now accessible: The Manage Delegation page is now ADA compliant. (refs PB-102920)

Admins

• Self-service settings can now be configured using .NET SDK: Integrators can now configure Self-service account settings using .NET SDK. (refs PB-92764)
• You can now configure the order in which senders and signers are displayed: Using the Account Configuration page you can now configure the order in which names are displayed. For example, First name, Last name, versus Last name, First name. Note that for signers, the change will only apply to newly added signers within new or existing transactions. (refs PB-98949)

• We have added additional permissions for template management: Administrators can now add template access permissions to a role. For example, from the OneSpan Sign UI admins can now configure a role so that a user can see the Templates menu, and from there create, update, and delete templates. Integrators using our APIs can define whether a user can create, edit, or delete templates. (refs PB-101046)

• We have added the ability to configure the browser tab title for the Signer Login page: You can now customize the browser tab title for both the Signer Login page, and in the Signer Experience. To customize your browser tab, contact our Support Team. (refs PB-103181)
• System Log Reports are now available: You can now retrieve logs related to user management events, as user management reports. These reports are generated as .csv files. The following events can now be retrieved: (refs PB-103295)
  • When senders reset their password using the Forgot your password feature.
  • When an account owner resets a sender's password.
  • User events, such as:
    • A user has been locked or unlocked
    • The status of a user changes
    • The user's type changes
    • Any password changes
    • A user has been deleted
  • Auto-provisioning during SSO authentication
  • Role creation, deletion, or updates

External Archiving

• We have improved the error message displayed when attempting to access the e-Vault Manager console: The updated message now explicitly states that e-Vault Manager has been deprecated. (refs PB-103196)

• The eOriginal Pre-Verify step is now configurable per account: You can now configure your account so that the eOriginal pre-verify check - the sanity check performed when a transaction is created - can be skipped. If skipped, the transaction will only be checked during the vaulting process. To enable this feature, contact our Support Team. (refs PB-104324)

• We have improved eOriginal's Retry Mechanism for Unexpected Errors: The eOriginal retry mechanism will now treat all unexpected errors as "recoverable" errors and will retry the failed action for the configured number of times (the retry is every 4 minutes up to 144 attempts). This will reduce the number of "unrecoverable" errors. Note however, that the LOGIN_FAILED error will now be treated as an "unrecoverable" error. This means that the retry mechanism will not attempt to retry the login action after a failed login attempt. (refs PB-104326)

Notarization & Virtual Room

• We have added participant instructions to RON transactions: While conducting RON transactions additional information now appears on the screen to help participants with the transaction work flow. For example, a message may appear indicating that the participant needs to upload an attachment. (refs PB-103724)

Senders

• Standardized Reporting Colors: To improve the consistency of our UI, we have standardized the color shading that appears when various elements within a report a selected. (refs PB-95345)

Signers

• Signers can now download the Evidence Summary: The Evidence Summary can now be downloaded from the Signer Experience once all participants have completed the transaction. To enable this feature, contact our Support Team. (refs PB-102006)
• External Hyperlinks can now be followed in the Signer Experience: External hyperlinks in document transactions can now be opened up by recipients who are signing those documents. To enable this feature, contact our Support Team . (refs PB-103397)

User Authentication

• You can now unlock LexisNexis: Signers who have failed KBA authentication using LexisNexis will now be locked (they can be unlocked). This means that the transaction can continue without having to create a new one. (refs PB-100507)

• OFAC verification results can now be seen in the Evidence Summary: OFAC (Office of Foreign Assets Control) verifications, both successful and unsuccessful, can now be seen in the Evidence Summary. (refs PB-102983)

• The OTP field is now masked for SMS Authentication: The OTP password is now masked when logging in. (refs PB-103301)

• Enhanced usability of the Create oAuth Client page: We have added the Client ID to the Create oAuth Client page. This makes it easier for you to copy this ID for your records. (refs PB-103865)

• oAuth 2.0 clients are now filtered by sub-accounts: If sub-accounts have been enabled for your account, the list of oAuth 2.0 clients is filtered to display only those clients connected to the selected sub-account. (refs PB-104226)

Bug Fixes

The following issues were resolved in this release:

Accessibility

• Screen readers now correctly read the Close button on the Re-send SMS dialog. Before, screen readers would read the Close button as Cancel. (refs PB-93193)

• A message now appears in the Designer if the maximum character limit is reached for a field. (refs PB-98795)

• Screen readers can now read the hand off dialog in IPEN and RON transactions. (refs PB-102656, 103937)
• There is no longer an accessibility issue with the Expiry Date column in the Transactions List. (refs PB-103408)
• There is no longer an accessibility issue with the pagination of the Transactions List. (refs PB-103409)

• We have fixed various accessibility issues that were reported when creating client apps and oAuth 2.0 clients. (refs PB-103774, 103777)

• For ADA compliance, any page or form that contains required fields marked with an * must show a text that says "Fields marked with * are required." This text has now been added to our Create Client App pages. (refs PB-103787)

• Screen readers can now read the contents of a Vulnerable Adult Questionnaire. (refs PB-103837)

• When changing the Sender language the aria label for the environment label would not translate without first performing a refresh. The language of the environment label now updates immediately. (refs PB-104125)

Admins

• Items within the Admin menu would sometimes require a hard refresh to appear properly when switching languages. Without the refresh these items would continue to appear in the previously displayed language. (refs PB-103376)
• Vulnerable Adult Questionnaire responses are now visible in the Journal. (refs PB-104170)

Evidence Summary

• There is no longer an extra View event displayed in the Evidence Summary. This would sometimes occur after confirming a signature. (refs PB-95343)

External Archiving

• The EDEPOSIT_SUCCESS callback is no longer omitted for some transactions using eOriginal workflows. (refs PB-104550)

Notarization

• An error message no longer appears when you change an IPEN or RON transaction to another type of transaction, and then reset the transaction back to the original IPEN or RON type. (refs PB-103833)

Senders

• An issue where an incorrect expiry date was displayed on the Create Transaction dialog when creating a transaction from a template with an unlimited expiry and a system level maximum expiry is defined has been fixed. (refs PB-100317)

• The Fast Track button no longer appears in the Sender UI if this feature has not been enabled. (refs PB-101635)

• An error message sometimes appeared when attempting to reactive an expired transaction. Senders can now set the expiration date of a transaction to the future, thus reactivating it in a Draft state. (refs PB-103576)

• Document zoom level is now maintained even if you re-size your browser in the Designer. (refs PB-103706)

• The Send to Signbutton in the Designer no longer changes position when changing your language to either Dutch or German. (refs PB-103830)

• The list of possible languages no longer flows past the length of the browser page when certain resolutions have been set. (refs PB-104617)

• When attempting to access the Sender UI after the session in a previously closed browser tab has expired, you are no longer asked to login twice. (refs PB-105762)

Signer Experience

• The signature box now maintains its size when uploading an image for your signature. (refs PB-93014)
• If the More Actions menu is hidden on the Signer Login page, the branding logo is now properly aligned. (refs PB-104269)
• In certain scenarios Reviewer type signers were taken to different documents, depending on whether other signers have completed their signatures. This no longer happens. (refs PB-104408)

Changed Behavior

Here are some of the changes in behavior that you might want to be aware of.

• You can no longer add a sender from a different account to a group. (refs PB-98152)

• As part of the new LexisNexis signer lock/unlock functionality, the authentication explanation included in the failure email has been updated to read "Failed authentication - The recipient failed to answer knowledge-based authentication questions correctly. Please review the sent transaction and update the recipient information or choose another type of authentication for the recipient." (refs PB-100507)

• Authentication questions and answers are now masked when using the GET /api/packages call. (refs PB-100530)

• With the introduction of our new template permissions it is important to note that when creating a custom role via integration that you must now include your desired template permissions. You should no longer rely on your existing Transaction permissions to determine whether or not templates are allowed to be created, updated, or deleted. (refs PB-101225)

• You can no longer enter negative values for reminders. For example, in startInDaysDelay, repetitionsCount, and intervalInDays. (refs PB-102670)

• The parameter Update Date in the payload of /api/packages/<package_id>/roles/<role_id> will be ignored, and the system date will be used instead. (refs PB-102670)

• To improve the consistency of our UI across different pages we have renamed the Create button in the oAuth 2.0 page to Add, and moved it above the list of oAuth 2.0 Clients. (refs PB-103548)

• We have updated the default From email addresses of customized email templates, but only if the From address is set to an esignlive domain. If it has been modified, or set to a parameter, we will not change it. The following From email addresses will be added (refs PB-103871): 

  • transaction-notifications@<domain>

  • account-notifications@<domain>

  • system-notifications@<domain>

  • The <domain> value is dependent on the environment you are using.

• Signers who have been designated as Reviewers only will now be taken directly to the first non-econsent document in the package. As they are not required to provide any consent they will not be presented with the Electronic Consent Document. (refs PB-104408)

• Handwritten signatures can no longer be fetched using the GET /api/packages call. (refs PB-105322)

Known Issues

Here are some of the known issues that we are currently working on, and plan to have fixed in a future release.

• eOriginal callbacks are reset when Event Notifications are updated and saved using the Event Notifications page. (refs PB-105022)
• The grant type for event notifications with oAuth 2.0 authentication is not set correctly when configuring using the Event Notifications page. (refs PB-105028)

• When registering an account, or when resetting the new account’s password, if another browser tab is already open with another session the user registering a new account or resetting the password will be logged into the already open session. Refreshing your browser resolves this issue. (refs PB-105804)

SaaS 2024-February: Release 24.R2.1 (11.56.1)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on April 26, 2024.

Changed Behavior

• PB-104595: Previously, when using callback notifications with OAuth 2.0 authentication, the Authorization Server URL would only retrieve access tokens that ended in /token. Now, it is no longer necessary to add /token to the end of the access token.

SaaS 2024-March: Release 24.R2 (11.56)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on May 9, 2024.

What's New

Signer Experience

• Spanish is now supported for recipients using LexisNexis for authentication: Recipients using LexisNexis for authentication can now receive authentication questions and answers in Spanish.
• Enhanced Transaction Declined Message: If a recipient declines to sign a transaction, thus making the transaction unavailable for other recipients, the remaining recipients will now receive a more detailed explanation as to why the transaction is unavailable to them.

Senders

• Added environment label: When working in a Sandbox environment a small 'SBX' label is now displayed in the upper left-hand corner of the UI.

• Added the ability to set Text alignment: You can now specify the alignment to be used for text within fields, when adding them to a transaction. For example, left, right, center, or justified. In addition, the default alignment can be set to Language dependent, meaning that the text alignment will follow the inherent layout of the transaction's language.

• Streamlined Recipient management: We have improved the way Recipients can be added, configured, and managed when creating or editing a transaction. Senders now have a quicker way of accessing various Recipient settings, resulting in a faster, smoother user experience.

Admins

• Added the ability to upload customized signature logos: Senders can now use the Account Configuration page to upload a customized signature logo for use in their transactions.

• Integrators can now use APIs to upload multiple documents, including Base64 documents: Integrators using either Java or .NET SDKs can now upload multiple documents to a transaction using a single SDK call. This includes Base64 documents.

• Added additional permissions for layout management: Administrators can now add Save Layout and Apply Layout permissions to a role. Note that these permissions will override any configurations made in the Designer, meaning that if, for example, a user does not have the Save Layout permission enabled they will not be able to save layouts, even if the Designer has been configured to allow that.

User Authentication

• Added the ability to make consent explicit: It is now possible to configure IDV transactions so that the consent given by recipients is explicit, meaning that they must actively perform an action to continue. For example, select a checkbox that confirms their consent. If explicit consent is not configured, recipients need only continue with the signing process, as their consent is deemed to have been implied. To configure this, contact our Support Team.

• Added self-serve configurations for OAuth 2.0: Admins can now configure their own OAuth 2.0 authentication settings, using the API Access page.

• Improved the counting of KBA authentication attempts : A KBA authentication attempt will now only be counted if a recipient actually attempts to answer a question. Previously, simply viewing KBA questions would count as an attempt, even if the recipient made no attempt to answer a question. This applies to non-RON transactions only.

Notarization & Virtual Room

• Added the ability to store recipient addresses: Notaries can now store a recipient's address. This address will now auto-populate future transactions and the eJournal if the same recipient is selected.

Trust Vault

• Added detailed information on deleted transactions: Users can now view information about deleted transactions, including the name of the user who deleted the transaction, the name and status of the deleted transaction, the date and time it was deleted, and the names of documents within the deleted transaction.

• Added detailed log information: Users can now view detailed log information related to a document in a transaction. This information includes the name of the user who performed any action on the document (such as downloading it), a short description of the action, the name of the transaction, and the date and time of the action.

Bug Fixes

User Authentication

• PB-99828: Fixed an issue where in certain situations an "Incorrect passcode" error message appeared after a signer had entered a SMS authentication code, but before they had hit enter to register the code.
• PB-101465: Fixed an issue where the data in various IDV columns in the Transaction Reports was not accurate.
• PB-103075: Fixed an issue where switching authentication methods on the Event Notifications page caused the UI to clear any previously changed entries. Now, you can change any entry and your changes will not be lost if you switch authentication methods.

Senders

• PB-92308: Disabled the ability to use Google translate in the Sender UI. Previously, using Google Translate in certain pages would result in an application crash.
• PB-99884: Fixed an issue where Field and Group tooltips were not immediately translated if the Designer language was changed.
• PB-100510: Fixed an issue where the Account Configuration page title was not fully displayed in certain languages.
• PB-100532: Fixed an issue where the KBA status message did not immediately update when changing the UI language. Users would have to refresh the page to see the KBA status in the newly selected language. Now, the field is updated immediately.
• PB-101458: Fixed a translation issue where country codes were not properly translated when using a Polish UI.
• PB-102456: Fixed a date format inconsistency issue. Previously, the date format used to search for transactions, templates, and journal entries did not use the same date format as the format for those entries in their various UI lists.
• PB-102743: Fixed an issue where a signer's name was not displayed in the Evidence Summary for geolocation.
• PB-102934: Fixed an issue where it was possible to paste more than the capped number of characters into the Signer Title field, and the Signer Company field. Rather than not allowing you to enter more than the allowable number of characters the UI would simply cut-off the extra characters upon saving. Now, you cannot paste in more than the allowable number of characters.
• PB-102980: Fixed an issue where the Actions column title in the Groups page was not fully displayed in certain languages.
• PB-103528: Fixed an issue where zooming in and out on a document in the Designer resulted in an inaccurate zoom scale being displayed.
• PB-103576: Fixed an issue that was preventing senders from reactivating expired transactions. This was caused by concurrency issues in the message queue threads.

Accessibility

• PB-98819: Fixed an issue with the alignment of words and sentences in the Electronic Consent Document when Accessibility Mode is enabled.

Signer Experience

• PB-95832: Fixed an issue where there appeared to be a slight delay in the appearance of a second signature field, after the first signature field had appeared. Now, all signature fields appear at the same time.
• PB-101485: Fixed an issue where the Continue button did not appear in transactions with a radio button and an optional signature.
• PB-101828: Fixed an issue where in certain situations a signer was not able to see a document that required their signature. This occurred in situations where an account was configured so as to prevent signers from seeing documents that did not require their signature, AND two signers with the same email address were assigned signatures in two different documents within the same transaction.
• PB-102335: Fixed an issue where an unexpected error was displayed when reassigning fields without a signature to a different signer.
• PB-102980: Fixed an issue where in certain situations clicking Next did not bring a signer directly to a signature field. Instead, the signer was brought to the page with the signature, but then had to scroll through the page to find the signature.
• PB-103178: Fixed an issue where the Signer Experience was zoomed in if an iPhone was used for authentication.

Admins

• PB-103104: Fixed an issue where some transactions were not being purged as per the account's Data Retention settings. This was due to an issue with the SQL query executing the process.
• PB-103115: Fixed an issue where adding a new Role name that exceeded the character length limit resulted in a missing translation error. Now, it is not possible to enter a Role name that exceeds the maximum character length.

Notarization

• PB-97980: Fixed an error where a validation error was shown when changing the type of transaction. This occurred when an IPEN or RON transaction was created with notarial signatures, changed to an IPEN transaction (which resulted in a validation error), and then changed back to an IPEN or RON transaction. In this scenario a second validation error erroneously appeared.
• PB-102099, 102485: Fixed an issue where it was not possible to select a notary with an active notary commission on the day that person's commission expires. For IPEN transactions, a validation error appeared. For RON transactions, the desired notary did not appear in the list of available notaries. Now, these notaries can be selected.
• PB-102072: Fixed an error where attempting to modify the Settings of a Placeholder recipient in a RON transaction caused the system to freeze.
• PB-102598: Fixed an error where it was possible to set a signer from a different account as a notary in your transaction, if that signer was a notary in that other account.
• PB-102646: Fixed an error where a notary signer in an IPEN transaction was not listed as the last signer.
• PB-102649: Fixed an error where the notary waiting room would briefly flash on screen before the notary journal loaded.
• PB-102747: Fixed an issue where an error would appear after changing a RON transaction's journal entry's language to Greek, if that transaction contained a video.
• PB-102748: Fixed an issue where the name of a recipient without signatures was displayed in the eJournal. Recipients who do not have signatures assigned to them no longer appear in the eJournal.
• PB-103306: Fixed an error where the Sign Notary Journal field was not immediately translated if a Sender switched UI language.

Vaulting

• PB-102599: Fixed an issue where a transaction appeared to have been vaulted twice in eOriginal.

Changed Behavior

• PB-98149: Users can no longer be assigned as delegates for other users on another account.

• PB-97276: The signer eid authentication column will be removed for transaction reports generated from June 2024 onwards. It will be replaced with three new columns: signer External Authentication, signer External Authentication type category and signer External Authentication type.

• PB-98153: Users can no longer be assigned the Manager role for a group that they are not part of.

• PB-101225: With the introduction of our new layout permissions it is important to note that when creating a custom role via integration that you must now include your desired layout permissions. You should no longer rely on your existing Transaction permissions to determine whether or not layouts are allowed to be saved or applied. This needs to be done via integration, or through the UI, as this permission is not automatically enabled.

• PB-101993: We have updated the default From and Reply To email addresses of our default email templates. The following From email addresses were added: 

  • transaction-notifications@<domain>

  • account-notifications@<domain>

  • system-notifications@<domain>

  The following Reply To email address was added:

  • do-not-reply@<domain>

  The <domain> value is dependent on the environment you are using.

• PB-102456: The date format for transactions, templates, and journal searches has been updated in the sender interface from dd-mm-yyyy to mm-dd-yyyy. Previously, the date format used to search for transactions, templates, and journal entries did not use the same date format as the format for those entries in their various UI lists.
• PB-102774: When accessing a declined transaction, signers will now get a Transaction Declined error page with a specific error message instead of the previous Unauthorized Access error page.
• PB-102421: In order to improve security, we have made the following changes:

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters in any field on the Personal Information section of the My Account page.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters as the name of an attachment requirement in a transaction.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters in the Comment field when rejecting an attachment uploaded by a signer.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters as the First Name, Last Name, Title, or Company of a recipient.

    These restrictions are applicable when creating or updating an item using the OneSpan Sign UI, or when updating an item using APIs.

Upcoming Changes

• PB-101224: In an upcoming release the API endpoint /api/account/accessibleaccounts will be modified so that using this call will only return the list of sub-accounts that the user making the call has access to. Currently, a list of all sub-accounts is returned.

• PB-103871: In an upcoming release we will update the default From email addresses of customized email templates, but only if the From address is set to an esignlive domain. If it has been modified, or set to a parameter, we will not change it. The following From email addresses will be added: 

  • transaction-notifications@<domain>

  • account-notifications@<domain>

  • system-notifications@<domain>

  The <domain> value is dependent on the environment you are using.

Known Issues

• PB-104354: The text alignment feature will always revert to Left in the Signer Title field, no matter what option is selected.
• PB-104459: The IDV Welcome Page event displayed in the Evidence Summary is not translated for certain languages.

SaaS 2024-March: Release 24.R1.6 (11.55.6)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Monday, March 18, 2024.

Bug Fixes

• PB-104100, PB-104101: Fixed an issue that was causing intermittent email failure when attempting to retrieve an OAUTH 2 token from Microsoft Online. To fix this issue we re-factored the token, and upgraded its library.

SaaS 2024-March: Release 24.R1.5 (11.55.5)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Friday, March 15, 2024.

Bug Fixes

• PB-104035: Fixed an issue where recipients were unable to view the Signer Experience when using a mobile device in an iFrame.

SaaS 2024-March: Release 24.R1.4 (11.55.4)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Monday, March 11, 2024.

Bug Fixes

• PB-103307: Fixed an issue that was preventing signers from using the Capture Signature from File option if their saved signature was over 500kb in size.
• PB-103646:Fixed an issue that was preventing documents from being loaded on the Designer. This occurred in certain situations where a Signer Title autofield was added to a document.
• PB-103715: Fixed an issue where an Access Denied error appeared in certain in-person transactions.

SaaS 2024-March: Release 24.R1.3 (11.55.3)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Tuesday, March 5, 2024.

Bug Fixes

• PB-103558: Fixed an issue where certain characters were not displayed correctly in documents, for both senders and signers.

SaaS 2024-February: Release 24.R1.2 (11.55.2)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Friday, February 22, 2024.

Bug Fixes

• PB-103434: Reverted a bug fix (PB-90883) from a previous release. The introduction of this fix resulted in the failure of transactions that used Change Signer and Text Tag Extraction together.

SaaS 2024-February: Release 24.R1.1 (11.55.1)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Friday, February 22, 2024.

Bug Fixes

• PB-103413: Fixed an issue with the GET /api/packages API call for transactions that was causing incorrect results to be returned when attempting to retrieve within a specified date range.

SaaS 2024-January: Release 24.R1 (11.55)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on Wednesday, March 5, 2024.

What's New

Trust Vault

• The OneSpan Compliance Vault has been renamed to Trust Vault : All UI instances of OneSpan Compliance Vault have been changed to Trust Vault.
• Transactions and documents can now be searched for and filtered: You can now search your transactions and documents by name, and then filter the search results to view by type (Transactions or Documents), by Anchor Status, and by Owner (if you have permission to view the transactions of other users).
• The Transactions page can now be filtered by owner: You can now filter the Transactions page by transaction owner (if you have permission to view the transactions of other users).
• Used account space is now available: The amount of space currently being used by an account is now displayed in the Trust Vault transaction list. This information is updated as documents are added or deleted.
• Transaction sizes are now available in OneSpan Sign reports: The size of Trust Vault transactions can now be seen in the In-App reports.
• Trust Vault is now available in our Interactive API: Trust Vault schema and responses can now be seen in our Interactive API. To view Trust Vault schema and responses, filter by Trust Vault.

Signers

• Increased length of Signer Title: You can now use up to 127 characters for a Signer Title.

Senders

• Added Created Date column to list of transactions: Transactions can now be viewed and sorted by the date that they were first created.
• PDF tooltips can now be extracted and imported into OSS tooltips: OneSpan Sign tooltips can now be auto-populated with a PDF's existing tooltips. This can be done using Document or Position extraction.
• Can now assign delegates for locked users: In situations where an account has been locked, Administrators and Managers can now assign delegates for that account. This is useful if, for example, a user has left the company.
• Users can now assign Delegates from within the Users page: If Roles and Permissions have been enabled, users can now use the Users page to assign delegates.

Admins

• Searching the Account Configuration Page now returns child settings: When searching for a setting on the Account Configuration page the search results now include any child settings of a search result, even if the child options do not match the search query.

User Authentication

• Reason for authentication failure now included in notification emails: Senders using the email.kba.failure template can now see the reason why a signer failed their KBA authentication. NOTE: If you are using a customized email.kba.failure template then you will need to contact our Support Team to use this feature.
• Added KBA authentication status for LexisNexis users: LexisNexis Senders can now see the KBA authentication status for each recipient in a transaction. For example, Successful, or Failed.
• Added OAuth 2.0 as a possible authentication method for callbacks: OAuth 2.0 can now be used as an authentication method for callbacks.
• Added the ability to define the authentication method used with callbacks: Administrators can now use the Event Notifications page to define the authentication method to be used with callbacks.
• Signers using LexisNexis for authentication now only need to authenticate once: LexisNexis Signers who use KBA authentication to access the Signing Ceremony now only need to authenticate themselves once, instead of each time they access the Signing Ceremony. NOTE: This does NOT apply to Remote Online Notarization transactions. Signers will still need to authenticate themselves when using RON.
• Simplified Evidence Summaries when using IDV for authentication: When using IDV as an authentication method, if the Document Authenticated matcher passes then the authentication is simply noted as having passed in the Evidence Summary. No additional information is provided. If the Document Authenticated matcher fails, then additional information will be provided.

Notarization & Virtual Room

• Can now filter, search, and sort notary journals: You can now use the Journals page to search for, filter, and sort your journal entries.
• Revamped IPEN solution: We have streamlined our In-Person Notarization process to make it more consistent with our Remote Online Notarization process.
• Setting up RON transactions no longer requires KBA for unknown signers: It is no longer mandatory to use KBA when creating a transaction with an unknown signer.
• Improved e-Journal experience: We have enhanced the e-Journal process, making it easier to select document and notarization types.
• Time format can now be configured:The time format for scheduling a Virtual Room session can now be configured to display in either a 12 hour format, or a 24 hour format. For example, 1pm, versus 13:00.
• Updated list of supported Notarization jurisdictions: We have updated our list of Jurisdictions that now support In-Person Notarization.
• Virtual Room and RON sessions will not time-out if a user is performing external authentication: In situations where a signer has been directed to an external resource for authentication purposes, such as to a different tab or web page, their signing session will no longer time-out because of inactivity. Instead, the signing session will time-out 15 minutes after the Host or Notary has left the session.

Bug Fixes

User Authentication

• PB-96559: Fixed an issue where the word "None" was not translated within the KBA provider drop-down list.
• PB-101281: Fixed an issue where the page to enter a phone number to be used for an IDV verification SMS was not appearing.

Senders

• PB-96226: Fixed an issue where the UI would crash when applying a layout where the transaction owner's email was associated with a different role.
• PB-96332: Fixed an issue that prevented users from assigning different languages to duplicate signers. This occurred when adding multiple external signers who have the same email address to a transaction. Attempting to assign a different language to one of the signers resulted in the language being changed for all signers with that email address.
• PB-99437: Fixed an issue which was causing the Save Layout and Apply Layout buttons to become disabled after flagging a recipient as a reviewer (Accept Only).
• PB-99395: Fixed an issue where the Sender UI allowed users to enter an empty space in the First or Last name fields. For example, by hitting a keyboard space bar. You must now enter a first and last name.
• PB-99440: Fixed an issue where a sender was not receiving the email.transaction.complete email. This occurred when a signer order had been set, and the sender was the last signer.
• PB-99752: Fixed a labeling issue for both Chinese Traditional and Chinese Simplified languages.
• PB-99754: Fixed an issue affecting Apple devices which caused documents in the Signer Experience to appear blurry or pixelated, disappear, or even crash completely.
• PB-99890: Fixed an issue where the expiry date for a transaction appeared in the Inbox for a transaction with a Draft status. This occurred when setting an expiration time in days. Transactions that are in a Draft status do not expire, and thus there should not have been a specified expiry date.
• PB-99955: Fixed an issue which made fields disappear when the transaction expired while still having an In Progress status.
• PB-99970: Fixed an issue where the Date field's size changed. This occasionally caused the field to change positions in a document.
• PB-99993: Fixed an issue where the French expiry date was not translated correctly within the email.delegation.activate email template when there was no expiry set for the delegation.
• PB-100010: Fixed an issue that was preventing the use of SMS authentication when the Sender had selected a non-existant country in their My Account profile.
• PB-100119: Fixed an issue where creating conditional fields using an API resulted in duplicated conditions when field names had matching starting characters.
• PB-100157: Fixed an issue where it was not possible to delete a field with conditional logic.
• PB-100158: Fixed an issue where the message "Expiry scheduled for null" appears in the UI when creating a transaction using a template with an expiration set for a number of days.
• PB-100312: Fixed an issue where the Sandbox watermark appeared twice on the French version of the Electronic Consent Document.
• PB-100367: Fixed an issue that was preventing integrators from updating or removing a Decline Reason using a PUT API call.
• PB-100442: Fixed an issue where changes to the expiration date, from a set date to unlimited expiration, are not remembered when creating a transaction from a template.
• PB-100483: Fixed an issue where users were allowed to enter an incorrect date when adding a delegate.
• PB-100515: Fixed an issue where an incorrect expiration date appeared on a template. This occurred when enabling and then disabling the Unlimited Expiration checkbox.
• PB-100618: Fixed an issue where you were not able to add a Placeholder type recipient from the Designer.
• PB-100647: Fixed an issue that caused issues with accessing FedRAMP Production environments.
• PB-100736: Fixed an issue that was preventing users from accessing the Transactions page.
• PB-100799: Fixed an issue where transaction owners were not able to download documents from their own transactions if the Display Download button setting in the Account Configuration page had been disabled. Transaction owners can now download their own transactions even if this setting is disabled.
• PB-101207: Fixed an issue where the search within the Inbox was not returning results when there was a very large number of transactions.
• PB-101145: Fixed an issue where customized roles could be assigned to users under different accounts. Customized roles can now only be assigned to users in the same account.
• PB-101206: Fixed an issue where in certain situations the Transactions Inbox would not display if Layouts had been disabled for the account.
• PB-101439: Fixed an issue where the SIGNER_COMPLETED event was not sent for a sender when a transaction with both Review Before Completion and a signing order were enabled.

Signer Experience

• PB-99591: Fixed an issue where text on certain documents appeared highlighted when accessed in the Signer Experience using older versions of iPhone iOS.
• PB-101521: Fixed an issue where Signers were experiencing Unauthorized Access errors. This was caused by an invalid token in the signing URL.

Admins

• PB-96623: Fixed an issue where the placeholder text and labels were not correctly translated on the Account Configuration page until the page was refreshed.
• PB-100235: Fixed an issue preventing admins and managers from assigning delegates for migrated sub-account users.

Vaulting

• OCV-657: Fixed an issue that was causing the dates and times that appeared in a Trust Vault Proof Certificate to display in English, even if the certificate itself was in French or Spanish.
• OCV-742: Fixed an issue where users were unable to delete their own transactions even if they had the Access and Delete Own Transaction permission enabled.

Accessibility

• PB-35943: Fixed an issue where there were no header labels for the input fields when adding recipients to a transaction.
• PB-93777: Fixed an issue where the error message that is sent when an invalid answer is provided in response to a Q&A authentication was not being read in full by certain screen readers. This occurred when using Windows 11 OS and iPhone 12 iOS.
• PB-96351: Fixed an issue where the sub-sections on the Account Configuration page were not being announced by screen readers. For example, Feature Settings > Email Documents.
• PB-99538: Fixed an issue where the More Actions menu button in the Signer Experience did not meet accessibility standards.
• PB-99602: Fixed an issue where field buttons in the Designer were not being announced by certain screen readers.
• PB-99604: Fixed an issue where tooltips were not being read by certain screen readers.
• PB-99605: Fixed an issue where the purpose of an asterisk next to a field was not being explained by screen readers. An asterisk next to a field indicates that this field is required, but this was not being announced by the screen reader. Now, the following text appears in the UI and can be read by screen readers: "Fields marked with a * are required".
• PB-99607: Fixed an issue where tab names (Drafts, Inbox, Trashed, Archived) were not announced by the JAWS screen reader on the Transactions page.
• PB-99608: Fixed an issue where table names were not defined and therefore not listed when accessing the Tables shortcut in the JAWS screen reader.
• PB-99991: Fixed the color contrast of the sign icon within the Transaction List so as to meet accessibility requirements.
• PB-101667: Fixed an issue where there was a discrepancy in the timestamp of the signing date when accessibility mode is enabled, versus the timestamp of the signing date when accessibility mode is disabled.

Performance Improvements

• PB-98332: Improved the performance of the Designer when using a document with a significant number of fields and conditional logic applied to it.

• PB-100941: Improved the performance of the Signing Ceremony during situations where a high volume of transactions that needed to be signed by a recipient occurred. Previously this resulted in a high CPU Load warning.

• PB-100355: Improved the performance of our Transaction Inbox.

• PB-100801: Improved the performance of our Dashboard.

Changed Behavior

• PB-93646: The PDF base-14 fonts Courier and Helvetica are now replaced in PDFs by the fonts LiberationMono and Liberation Sans, respectively. This ensures that these fonts will be embedded in the PDF, and that documents will look the same across all PDF viewers and operating system platforms. Note that this is only relevant for text form fields, watermarks, and signatures. The actual text of a document is not affected.
• PB-98498: The Event Notifications page now has a drop-down menu that can be used to select an authentication method. NOTE: If no Callback Key has been defined the authentication method will be set to None. If a Callback Key has been defined, then the authentication method will be set to Basic. In addition, OAuth 2.0 is now available as an authentication method.
• PB-99395: When editing your My Account information, a first and last name is now required. For existing Senders who were created without a first or last name, you can not edit those Senders without adding a first or last name.
• PB-101707: Upon completion of an In Person Notarization (IPEN) session a notary can now click a button and be redirected to their e-Journal.
• PB-100793: It is now possible to turn off enforced authentication for RON and IPEN transactions.

Upcoming Changes

• Our Text Alignment feature will not be deployed in Release 24R1 (11.55) Production environments, but will be available in a future release.
• In Release 24.R2 (11.56), all references to Equifax will be removed from the code base. Any integration code (APIs and SDKs) that references Equifax as a recipient authentication method will need to be removed.

Known Issues

• PB-99976: Using the Designer to set a default value for text fields higher than 1024 characters results in an error message. However, if you set the default value to 1024 characters your signers can still enter up to 4000 characters in the Signer Experience.

SaaS 2023-December: Release 23.R5.1 (11.54.1)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on December 4th, 2023.

Bug Fixes

• PB100891: Fixed an issue where using a GET /api/account/senders/{roleID} call to retrieve all senders in a sub-account only returned senders who were first created in that sub-account. Now, this call will return all senders in that sub-account, even if they were first created in another sub-account, and then subsequently given sender permission for the sub-account the call is targeting.

SaaS 2023-October: Release 23.R5 (11.54)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on November 13th, 2023.

What's New

Trust Vault

Introducing Trust Vault: Trust Vault enables organizations to securely store critical signed and completed digital agreements ensuring long-term viability and integrity that withstands the test of time.

Supported functionalities include:

• Out of the box integration with OneSpan Sign
• Granular user access management through OneSpan Sign Roles and Permissions functionality
• Irrefutable Proof Certificate

To enable Trust Vault on your OneSpan Sign account, please contact our Support Team.

If sub-accounts are enabled, Trust Vault cannot be used.

Languages

• Support for three more languages: We added support for the following languages: (1) Bulgarian; (2) Romanian; (3) Norwegian (Bokmål). Note: (1) Due to certain Canadian SMS guidelines, SMS messages sent in Romanian or Norwegian to Canadian phone numbers via Twilio's messaging service will be received in English. (2) Twilio does not support Bulgarian. Thus SMS messages sent in Bulgarian via Twilio's messaging service will be received in English.

If you have any customized email templates that you would like to use with these newly added languages, please contact our Support Team. If you do not contact our Support Team, the default OneSpan Sign email templates will be used.

Senders

• Increased OSS Email File Attachment Size: Senders can now configure the file sizes that emails can support. To do this, contact our Support Team.
• Added support for tooltips on Fields: Senders can now add tooltips to Fields in a transaction, which will be displayed or read in the Signer Experience when a reader hovers over or tabs to that field. Tooltips can be used to add additional context or instructions to a field, thus improving the user experience.
• Added checkbox to allow for transactions that do not expire: Previously, to create or edit a transaction so that it does not expire, or to set a default value for an account so that transactions associated with that account do not expire, Senders had to enter a value of '0' in the Expiration field. Now, Senders can simply use the checkbox to create transactions that do not expire.
• Added ability to assign delegates from Users page: You can now assign delegates using the Users page.
• Sender details can now be seen on the Users page: You can use the Users page to view additional information on a selected Sender.
• Removed references to Opt out: References to the deprecated feature "Opt out" that appeared in the Usage Summary report have been replaced by "Decline to Sign".
• Re-branded Activation and Expiration emails: The account activation and expiration email templates have been updated to reflect our latest corporate branding.
• Improved Designer performance when using Conditional Logic: The performance of the Designer was significantly improved in situations where many fields with conditional logic had been applied to a document.

Admins

• All blacklisted attachments are now displayed: When configuring your Upload Settings a complete list of blacklisted attachments is now displayed. This includes both the default blacklisted attachments, as well as any account specific blacklists.
• Disabled features are no longer available when viewing using the Self Service Account Configuration: When using the Self Service Account Configuration page features that have been disabled because of a previously configured setting are no longer available to edit. For example, if the feature Enable document visibility is disabled, then the feature Allow configuring document visibility will be grayed out.
• Self-service settings can now be configured using Java SDK: Integrators can now configure Self-service account settings using Java SDK.

User Authentication

• Implemented callback and email notifications for LexisNexis failures: Callbacks and emails will now be sent when the following scenarios are met:
  • Signer failed to authenticate.
  • Signer not found in LexisNexis database.
  • Signer does not have enough information associated with them and thus LexisNexis was not able to generate any authentication questions.

    For more information, see email.kba.failure

• Enhanced SSN authentication with KBA with LexisNexis: When setting up KBA with LexisNexis, it is now possible to provide a Social Security Number for a Recipient in three ways:
  • No SSN
  • Full SSN
  • Last four digits of SSN
• Enhanced Identity Verification: Additional verification results can be included in the Evidence Summary. These are:
  • Verification Results: Show the checks and matches used to determine if the verification should pass or fail.
  • Personal Information: Show the data extracted from the document presented, about the identity. For example, Name, Date of Birth.
  • Document Information: Show the data extracted from the document presented, about that document. For example, Country, Type, Issue Date.

    These features are enabled by default. To disable any of these features contact our Support Team.

• Additional information available in the Evidence Summary and IDV Evidence Summary JSON: The following information is now available for viewing:

  • The IDV Evidence Summary PDF now displays the Document_Authenticated matcher only.
  • The IDV Evidence Summary now includes the signer ID in its JSON API.
  • The IDV Evidence Summary now includes the number of verification attempts in the list of image URLs JSON and the JSON API.

Accessibility

• Enhanced Document screen-readability: We have enhanced the screen-readability of documents in the Signer Experience. Screen readers can now read through a transaction's documents and fields without requiring the signer to switch to Accessibility Mode, and without requiring the Sender to create an accessible transaction. During this process, the screen reader will tell the signer if the document can be read by the screen reader.

  If full accessibility is a requirement for your organization, then you must create accessible transactions using properly tagged documents.

• Improved wording on document accessibility toggle: We have changed the label used to create an accessible transaction and improved the accompanying tool-tip for an enhanced user experience. The toggle now says Enforce document accessibility instead of Enable Accessibility.
• Made the following Designer page icons 'bolder' to satisfy WCAG Accessibility standards for color contrast:
  • Apply layout icon
  • Document visibility icon
  • Keyboard shortcuts icon
  • Save layout icon
  • Settings icon

Notarization & Virtual Room

• RON supports three more U.S. States: We added the following States to the Jurisdiction drop-down list that the system presents to notaries when they register their Notary Commission: (1) Louisiana; (2) Rhode Island; (3) Kansas.
• Added support for External Signer Verification for VR and RON Signers: It is now possible to setup External Signer Verification for Signers signing Virtual Room and RON transactions. Note that the account must be configured to use an external verification service. If configured, when signing and after clicking Confirm document, the Signer will be directed to the external verification service, which will open in a new browser tab.
• In RON transactions, the State/Province field is now associated with the Country field: When creating a RON transaction the State/Province field will now display the regional jurisdiction that is relevant to the selected country. Thus, if USA is selected as the country, the State/Province field will show States. If Canada is selected, Provinces will be displayed. For other countries, users can enter the proper value themselves.
• Notary field values are now visible on documents: When accessing the documents, notary fields will now be visible, even before confirmation. The following notary values are displayed:
  • Notary Country
  • Notary Jurisdiction
  • Notary Commission Expiration Date
  • Notary Commission Number
  • Notary Name
• New process for applying a Notarial seal: After a notary finishes signing a document an Apply Seal button will appear. Once clicked, the documents will be confirmed and the Notarial Seal will be applied and rendered on the document.
• Enhanced user experience for in-person and in-person Notarized transactions: Adjusted the look and wording on affidavits for in-person, and in-person Notarized transactions.
• New email template for in-person Notarized transactions: When a Signer is invited to a in-person Notarized transaction the email the Signer receives will allow them to review the documents in the transaction, but not begin the signing process. Signing can only take place in the presence of the notary. For more information see email.activate.ipen
• Enhanced user experience for notaries initiating a Signer Experience. Notaries now:
  • See a configuration screen that invites them to setup or configure their audio and video settings.
  • See the status of signers in the transaction waiting room.
  • See a transaction overview page that will aid them in running the Signer Experience.

eOriginal Integration

• Added ability to use their own transaction type name when using vaulting: Vaulting customers can now pass their desired transaction type name to our system using the transactiontypename parameter. This allows users to distinguish the source of certain transactions when vaulting from multiple sources they want to track.
• Enhance error handling for bad or incomplete vaulting data: Error handing has been improved to include more information for the customer use. This includes more information about the error, along with error callbacks and email notifications.
• Enhanced vaulting robustness and reliability: The vaulting experience has been enhanced with the following:
  • Retry time changed from 1 hour to 4 minutes
  • New retry attempt callback
  • Improved success, failure and retry callback verboseness
  • Improved logs

External Archiving

• Added a second connector for SFTP with the option of obtaining a NOM 151 certificate: In 11.52 we added Arkhineo as an integration connector. You can now use SFTP as an integration connector as well, while also having the option of obtaining a NOM 151 certificate. To enable this feature, contact our Support Team.

Bug Fixes

User Authentication

• PB-97932: Fixed an issue where in certain scenarios the Signing logo did not display on the KBA authentication page.

Senders

• PB-96825: Fixed an issue which was preventing users from updating a transaction's status to SENT via the API.
• PB-97293: Fixed an issue where a user could not update a template's name. This occurred when attempting to change the case and only the case of any letter in the template (for example, from upper case to lower case).
• PB-97435: Updated the wording in a confirmation message that appeared when deleting a transaction.
• PB-97725: Fixed an issue where the maximum length of 64 characters was not being respected when multi-byte characters were used.
• PB-98011: Fixed an issue where it was possible to retrieve attachments from a deleted transaction.
• PB-98502: Fixed an issue where a blank screen would appear when attempting to reassign a recipient on a mobile device.
• PB-98918: Fixed an issue where setting the Group Validation Range for some checkboxes to '0' resulted in a "Something went wrong" error message. Now, a warning message appears telling the Sender that you cannot set this range to zero.
• PB-99039: Fixed an issue where attachment requirements could not be added for a recipient from the Designer.
• PB-99190: Fixed an issue where it was possible to obtain a valid transaction ID when making an API request with faulty information.
• PB-100585: Fixed an issue which was causing a security vulnerability in relation to one of our GET API calls.

Connectors

• PB-97618: Fixed an issue in which the default banner did not appear if the Designer was integrated inside a Salesforce iFrame.

• PB-98482:Fixed an issue which was preventing the creation of transactions from templates when using OneSpan Sign Embedded Integration for Salesforceand OneSpan Sign Embedded Integration for CRM connectors with Roles and Permissions enabled.

Signer Experience

• PB-98089:Fixed an issue where default values defined by the Sender for list fields and their options do not appear in the Signer Experience. The fields appeared, but the default options did not.
• PB-98146, PB-96342: Fixed an issue where the Accept bar no longer appeared on a short Electronic Consent Document if a session expiry message was dismissed, or if a cookie notification was dismissed.
• PB-95888: Fixed an issue where the More Actions menu was not displayed when accessing the Signer Experience from the Rejected Attachment email.
• PB-96288: Fixed an issue where the More Actions menu was not hidden in the Signer Experience when there are no options available to select.
• PB-98382: Fixed an issue where the signer was not prevented from making changes to input fields on a document when a document was confirmed.

Admins

• PB-96303: Fixed an issue which was causing a significant delay (lag) when adding a new role to a user. This occurred when Roles and Permissions was enabled and they attempted to do so using an Admin's API key.
• PB-96909: Fixed an issue that where an Invalid JSON error occurred when setting certain properties to 'null' within packagesettings and then making changes using the Self Service Account Configuration.
• PB-98288: Fixed an issue where the Senders page did not properly display column headers in certain languages, most notably Dansk, Nork, or Greek. In these situation, the last column (Actions) was sometimes truncated.
• PB-99187: Updated the Add a checkbox to the top of the Consent document description in the Self-Service Account Configuration page.
• PB-100060: Fixed an issue that was preventing Sub-Account enabled accounts from creating transactions using Bulk Send.

Vaulting

• PB-98570: Fixed an issue where document vaulting was triggered multiple times.

Accessibility

• PB-98223: Fixed an accessibility issue regarding the color contrast of icons displayed within the Transaction list.
• PB-98283: Fixed an accessibility issue regarding the color contrast of the View all link on the Dashboard.
• PB-98355: Fixed an accessibility issue regarding the color contrast of the links within the application footer.

Changed Behavior

• PB-93756: The format for all date fields in exported CSVs are now set to yyyy-MM-dd HH:mm:ss.
• PB-98015: The label for the PACKAGE_RESTORED callback in the Event Notification page has been changed from Transaction Unarchived to Transaction Restored.
• As part of transaction expiry re-factoring, account settings are now checked when creating a transaction even if a previously created template was created with unlimited expiry.

Technology Updates

• PB-100182: Added support for eOriginal cookies. This ensures that any integration with eOriginal is maintained during any infrastructure updates.

Known Issues

• PB-100157: An error occurs when attempting to remove a field with conditional logic from a transaction that has already been sent. To resolve this issue, dismiss this error and then remove the field again. The field will be successfully removed.
• PB-100050: The link to open the Trust Vault appears in English only, no matter what language is selected for the UI.
• PB-100357: Administrators and Managers cannot assign delegates for locked or disabled users. This issue will be fixed in a future release.
• PB-100235: Administrators and Managers that were created after Roles and Permissions have been activated cannot assign delegates from the Users page. This issue will be fixed in a future release.
• PB-100635: Attempting to use the Users page to assign delegates to sub-account users results in a 404 error. This issue will be fixed in a future release.
• PB-100497: An error occurs when users who have Customized Roles attempt to use the Users page to assign delegates for other users. In a future release the ability of users with customized roles to assign delegates for other users will be removed (though they will still have the ability to assign delegates for themselves).

SaaS 2023-September: Release 23.R4.1 (11.53.1)

This is a security patch release.

SaaS 2023-September: Release 23.R4 (11.53)

What's New

Knowledge-Based Authentication

• Equifax US replaced by LexisNexis: Equifax US has been replaced by LexisNexis. Any account that had Equifax US enabled will now have LexisNexis enabled by default. Senders will be notified of these changes if they try to do either of the following: (1) send transactions with Equifax US as an authentication method; (2) update signers who have Equifax US as their authentication method. Signers who try to authenticate themselves via Equifax US will now: (1) be notified that they cannot access the associated transaction; (2) be asked to contact the transaction's sender. Important: In this release: (1) signers’ authentication status is not available with LexisNexis; (2) failure callbacks and emails are not supported with LexisNexis.
• Equifax Canada deprecated: Equifax Canada is no longer supported, and will not be replaced with another service.

ID Verification

• New APIs for ID Verification: Three new API's download the following items, respectively: (1) an Evidence Summary in JSON format that contains detailed ID Verification information; (2) one specified ID Verification image; (3) multiple ID Verification images that have been specified in a list.

Languages

• Support for three more languages: We added support for the following languages: (1) Polish; (2) Spanish (Spain); (3) English (United Kingdom). Note: (1) Due to certain Canadian SMS guidelines, SMS messages sent in Polish to Canadian phone numbers via Twilio's messaging service will be received in English. (2) Twilio does not support Spanish (Spain). Thus SMS messages sent in Spanish (Spain) via Twilio's messaging service will be received in Spanish (Latin America).

If you have any customized email templates that you would like to use with these newly added languages, please contact our Support Team. If you do not contact our Support Team, the default OneSpan Sign email templates will be used.

Senders

• Senders can configure Designer settings: Self-Service Account Configuration now has a group of Designer Settings that determine the functionality of the Designer page.
• Senders can configure upload settings: Self-Service Account Configuration now has Upload Settings that specify the file types that recipients can upload as attachments.
• Senders can configure email reminders: Self-Service Account Configuration now has Email Reminders that specify a schedule for email reminders that will be sent to all recipients who have not yet finished signing.
• Better Event Notification page: We redesigned the Event Notification page that senders use to configure event notifications for their listener services. The new design is more logical and less confusing.

Admins

• Can customize Electronic Consent’s Accept button: Admins can now specify the text on the Accept button in the bottom bar of the Electronic Consent document. This button no longer needs to be the same as the Accept button for Accept Only recipients. To customize this text, Admins will need to work with our Support Team.

Remote Online Notarization

• RON supports five more U.S. States: We added the following States to the Jurisdiction drop-down list that the system presents to notaries when they register their Notary Commission: (1) Michigan; (2) Missouri; (3) New Mexico; (4) Pennsylvania; (5) Wisconsin.
• Two main authentication options: When senders configure the Authentication Method for a participant in a RON transaction, they are now presented with the following two options: (1) Unknown Signer — in this case, the sender must specify the methods KBA Authentication (via LexisNexis) and ID Verification; (2) Personally Known Signer — in this case, the sender can specify any Authentication Method (or none at all).
• KBA respects the notary’s jurisdiction: The KBA Authentication Method used in a RON transaction is now customized to meet the requirements of the jurisdiction where the notary has their commission.
• Better Locked Out error page: When a user is locked out after an unsuccessful authentication attempt, the Locked Out error page now shows how much time remains until the user will be permitted to make their next authentication attempt.
• Notary Journal can record document dates: The Notary Journal now has a field that notaries can use to enter the date that appears on a document they are notarizing. This is useful because that date sometimes differs from the date when the notarization is performed.
• Can require participants to sign Notary Journal: A new feature enables senders to require that a RON transaction’s participants sign the Notary Journal. If a sender makes this requirement, during the transaction the notary can: (1) make their journal entries; (2) then pass control to the participants so they can sign the journal. To enable this feature, please contact our Support Team.
• New way to access the Thank You page: When a notary is reviewing a completed RON transaction, the Thank You page now opens after they click the Finish button on the last document. Note: That page has always opened — and it still does — when the notary clicks the Finish button in the Notary Journal.
• Reminders about Notary Commission expiry: Notaries will now get emails to remind them of the approaching expiration of their Notary Commission. These emails will be sent 90, 60, 30 and 7 days before expiration.
• Can set Notary Commission expiry to N/A: Notaries can now configure their commission’s expiration date as N/A (Not Applicable). This is useful because in some jurisdictions (e.g., Canada) commissions do not expire.

In-App Reporting

• New column in Transaction Reports: We added a Transaction Description column to Transaction Reports. Note: (1) This column will appear only for ongoing and future reports; (2) for ongoing reports, the column will be populated only if the transaction has been updated.

Bug Fixes

Free Trial

• PB-97466: Fixed an issue in which a link in the activation email for a Free Trial of OneSpan Sign failed to redirect users to the Account Registration page.

User Authentication

• PB-96316: Fixed an issue in which completing an ID Verification process triggered an Internal Server Error. This error was caused by the fact that a Redis key/value had not expired.
• PB-97838: Fixed the following issue. When a signer uses Client App credentials to generate a Signer Authentication Token, the system should not send an SMS OTP (one-time password) to their mobile phone. The problem was that the system did that.
• PB-92243: Fixed an issue in which the signer's authentication page appeared in English, but should have appeared in the transaction's language (French). This occurred when: (1) the transaction was created via the SDK; (2) the signer’s language was not specified.

Senders

• PB-97194: Fixed the following issue. In Self-Service Account Configuration, the transaction setting Allow document download for incomplete transactions was working with "reversed logic". In other words, the problem was that the functionality was allowed when unchecked, and not allowed when checked.
• PB-97570: Fixed the following issue. An account’s default language was set to a language other than English. A sender on the account then created a transaction via the API, but did not specify a language. In this situation, the transaction's language should have defaulted to the account’s default language. Instead, it defaulted to English.
• PB-94961: Fixed the following issue. In the Designer’s Apply Layout dialog box, if the toggle switch Show shared layouts is ON, the Select a layout drop-down list should display all shared layouts. The problem was that this list didn't display any of the existing shared layouts.
• PB-96940: Fixed an issue in which trying to create a transaction via the API failed when: (1) the feature Allow Duplicate Signers was enabled; (2) the feature Allow Duplicate Signer Phone Number was disabled.
• PB-94744: Fixed the following issue. The feature SSO Login was enabled, so senders had to log in to OneSpan Sign via Single Sign-On Authentication (SSO). The feature auto-provisioning was disabled, so an SSO login did not automatically create a new sender if one did yet not exist in the system. In this situation, after a user’s first successful SSO login, they were trapped in the state Pending. To fix this, we changed the API. Now, after a user’s first successful SSO login, their status is automatically set to Enabled (active). Note: This fix does not change anything for use cases where the Roles and Permissions feature is enabled.
• PB-96189: Fixed an issue in which using a Fast Track link to create a template triggered an error when the following features were enabled and used: (1) Delegation; (2) Roles and Permissions; (3) Sub Accounts.

Signer Experience

• PB-97932: Fixed an issue in which the logo failed to appear on the Signer Login page when the logo’s SVG file was missing the width attribute.
• PB-97442: Fixed an issue in which a captured signature sometimes appeared too small or was not visible before being confirmed.
• PB-96886: Fixed an issue in which the system failed to enforce a minimum length for captured signatures.
• PB-95644: Fixed an issue in which an error message appeared in English, but should have appeared in French. The error message appeared after a signer tried to decline a completed transaction.
• PB-93727: Fixed an issue that arose in the following situation. (1) Within a transaction, a signer delegated their signing responsibilities to a new signer (using More Actions > Reassign Recipient). (2) The original signer then finished reviewing the transaction’s documents, and clicked Finished. (3) The Thank You page that then appeared should have displayed the name of the original signer. Instead, it displayed the name of the new signer.

Admins

• PB-96415: Fixed an issue that occurred when the Roles and Permissions feature was enabled, then disabled, then enabled again in OneSpan Sign BackOffice. By this point, the system had made the mistake of adding default roles to users.
• PB-87067: Fixed a OneSpan Sign BackOffice issue in which trying to download an Electronic Consent document triggered an HTTP 500 error.

Remote Online Notarization

• PB-96361: Fixed an issue in which notaries couldn't return to the Overview page after starting a RON transaction. We fixed it by restoring the left sidebar’s Home button.
• PB-93258: Fixed an issue in which a RON transaction’s Thank You page did not display properly on certain mobile devices.
• PB-97304: Fixed an issue in which KBA error pages in RON transactions failed to match RON’s current design.

Accessibility

• PB-95925: Fixed an issue in which a Screen Reader failed to read the contents of a signed document's Date field.

Language

• PB-97202: Fixed an issue in which Japanese email notifications displayed expiry dates in English.

Changed Behavior

• When setting SMS authentication for a recipient, the country code will default to the country set for the Sender within their account profile. If their country is set to Other (which is the default), the SMS input country code will be set to International.
• Equifax US and Equifax Canada are no longer supported.
• When using LexisNexis KBA, signers are now authenticated each time they access the signing link, regardless of whether or not the signing has been completed.
• If a signer fails to authenticate using LexisNexis KBA, the sender will need to create a new transaction if they want to re-attempt KBA authentication.
• OneSpan Sign now supports only the latest stable version of its supported browsers (Chrome, Firefox, Edge, Safari). This applies to both the Signer Experience and the Sender part of the New User Experience.
• PB-97114, PB-95121: The Evidence Summary now records if the selfies and documents submitted during ID Verification are authentic.
• PB-97194: In Self-Service Account Configuration, the transaction setting Allow document download for incomplete transactions has been renamed Disable document download for incomplete transactions.
• PB-97112: In Self-Service Account Configuration, the system setting Transaction expiry warning (days) has been removed.

Upcoming Changes

• PB-93756: Starting in Release 23.R5 (11.54), the format of all Date fields in exported CSV files will be "yyyy-MM-dd HH:mm:ss". This applies to the following CSV files: (1) Notary Journal Export; (2) Transaction Usage Report; (3) Transactions Scheduled Report; (4) Account Scheduled Report.

SaaS 2023-August: Release 23.R3.1 (11.52.1)

Bug Fixes

Accessibility

• PB-97462: Fixed the following issue. The signatures applied to a document in an accessible transaction were invalid if: (1) the Sender added to each Signature Field a Signing Date autofield; (2) the Signature Fields were signed in an order that differed from the order in which these fields had been added to the document.
• PB-97438: Fixed the following issue. An accessible transaction had two signers, and each Signature Field was assigned one Signing Date autofield. Each applied signature should have carried information about the fields locked to it, but this information was either missing or incomplete.
• PB-97203: Fixed the following issue that occurred in an accessible transaction. In a signed document, where a single Signing Date autofield should have appeared, two Signing Date autofields appeared. Moreover, these autofields overlapped.
• PB-97905: Fixed the following issue. A user downloaded a signed document that was part of an accessible transaction that had two signers, two signatures, and a Signing Date autofield for each signature. The downloaded document wrongly indicated that two Form Fields had undergone "Property Changes".

Printing

• PB-96480: Fixed a printing issue that was caused by a missing XObject.

Upcoming Changes

• PB-93756: Starting in Release 23.R5 (11.54), the format of all Date fields in exported CSV files will be "yyyy-MM-dd HH:mm:ss". This applies to the following CSV files: (1) Notary Journal Export; (2) Transaction Usage Report; (3) Transactions Scheduled Report; (4) Account Scheduled Report.

SaaS 2023-July: Release 23.R3 (11.52)

Upcoming deprecation of Equifax Canada: After September 6, 2023, when Senders specify a KBA authentication method for a transaction recipient, they will no longer be able to select Equifax – CA as the KBA provider. If after that date users access an incomplete transaction with Equifax – CA selected, they may experience an error. To avoid such errors, we recommend that you: (1) change the authentication method for any such transaction that has been sent; (2) not select Equifax – CA for new transactions. If you have any questions, please contact our Support Team.

What's New

External Archiving

• External Archiving: The documents from all of an account’s completed transactions can now be stored in the vaults of Arkhineo, a block-chain service for long-term document storage. To track this archival process, we’ve created the following statuses: (1) ARCHIVAL_PENDING; (2) ARCHIVAL_VALIDATING; (3) ARCHIVAL_INTERVENTION_REQUIRED; (4) ARCHIVAL_COMPLETE. To enable this feature, please contact our Support Team.

Senders

• Senders can configure more transaction settings: Senders can now configure the following transaction settings using Self-Service Account Configuration: (1) Allow document download for incomplete transactions; (2) Display document name on each page of the document; (3) Display signing progress; (4) Allow recipient to navigate across actionable fields in the document; (5) Include optional fields in navigation; (6) Limit number of files per attachment; (7) Font size.
• Senders can configure new system settings: Senders can now configure the following system settings using Self-Service Account Configuration: (1) Maximum login attempts for a sender; (2) Session expiry; (3) Session expiry warning.
• Senders can configure Enable Recipient History: Senders can now configure the feature Enable Recipient History using Self-Service Account Configuration. This feature determines if an account’s Senders will be able to see the account’s recipient history.
• Improved dependent settings: We improved the following aspect of the Self-Service Account Configuration’s User Experience. Previously, when one setting depended on another, a warning message appeared. Now, a dependent setting is: (1) indented under its parent; (2) automatically enabled or disabled based on the parent setting.
• Can duplicate Imprint Fields: Senders can now duplicate Imprint Fields – i.e., fields that transaction recipients can see, but cannot interact with in any other way. The duplication procedure is the same as for other fields — i.e., within the Designer: (1) select one or more Imprint Fields; (2) open the Field Settings pane, and click Duplicate.
• New types of Imprint Fields: Senders can now add the following types of Imprint Fields to documents: (1) TransactionID; (2) DocumentID. These fields are automatically populated, and their values cannot be changed.
• Rebranded colors: To reflect OneSpan’s new colors, we rebranded: (1) the checkboxes in the Sender part of the New User Experience; (2) "selected" radio buttons in the Designer.

Signer Experience

• Better placed Get Started button: We improved the visibility of the Get Started button on iPhones, so users wouldn’t think that they were "stuck" and thus unable to enter the Signer Experience.

• More granular control of duplicate signers: Before Release 11.47, a transaction's recipients could have: (a) the same full name OR the same email address, but not both simultaneously; (b) the same phone number. We call this the system's "legacy behavior” regarding duplicate signers.

Release 11.47 introduced the BackOffice setting Allow Duplicate Signers. When enabled, this setting allowed a transaction's recipients to have: (a) the same full name AND the same email address simultaneously; (b) the same phone number.

This release provides more granular control of such duplicated information via the following BackOffice settings: (1) Allow Duplicate Signer Email Address — Determines if a transaction's external recipients can have identical email addresses (default = enabled). (2) Allow Duplicate Signer Name — Determines if a transaction's recipients (external and internal) can have identical full names (default = disabled). (3) Allow Duplicate Signer Phone Number — Determines if a transaction's recipients (external and internal) can have identical phone numbers (default = enabled). (4) Allow Duplicate Signers — This setting is now a master switch (default = disabled). If it’s enabled, the previous three settings are honored. If it’s disabled: (a) the previous three settings are ignored; (b) the setting’s "legacy behavior" is restored.

Caution: The "duplicate signers" feature does not work with Single Sign-On Authentication (SSO).

Note: OneSpan Sign uses phone numbers only for SMS authentication and ID Verification.

Account Owners & Admins

• Can specify the language for redirect URLs: Account Owners and Account Admins can now specify the language of redirect URLs, so Senders and Signers can be redirected to pages in their preferred language. Such URLs include Sender Logout, Sender Session Timeout, and Signer Session Timeout. To configure this feature, please contact our Support Team.

Developers

• SDK can configure more settings: The SDK can now be used to configure the feature Enable Recipient History, and the following transaction settings: (1) Allow document download for incomplete transactions; (2) Display document name on each page of the document; (3) Display signing progress; (4) Allow recipient to navigate across actionable fields in the document; (5) Include optional fields in navigation; (6) Limit number of files per attachment; (7) Font size.

Remote Online Notarization

• RON supports five more U.S. States: We added the following States to the Jurisdiction drop-down list that the system presents to notaries when they register their Notary Commission: (1) Idaho; (2) New Hampshire; (3) New Jersey; (4) North Dakota; (5) Wyoming.
• Reminder for Notary Seal & RON Statement A reminder now appears when a Sender tries to send a Remote Online Notarization transaction without having added a Notary Seal and RON Statement to the transaction’s documents. The popup reminds the Sender that some U.S. States require these additions.
• System copies available signer information: This feature concerns Remote Online Notarization transactions in which a signer is assigned KBA authentication. To save Senders from having to enter a signer’s information twice, if the Sender enters Recipient Details about a signer when they create the transaction, the system now: (1) copies those details into the corresponding fields for KBA authentication; (2) permits Senders to edit the copied information (e.g., First Name, Last Name, City, State, Zip code).

Remote Online Notarization & Virtual Room

• Better interface for failed authentication attempts: If the recipient of a RON or Virtual Room transaction is using an Authentication Method that limits the number of failed attempts, now when an authentication attempt fails: (1) the system displays the number of remaining attempts; (2) a Retry Authentication button appears. If the user clicks that button, they can try to authenticate themselves again without affecting the number of remaining attempts.

Evidence Summary

• Enhanced Evidence Summary: To ensure compliance with KYC (Know Your Customer) regulations in multiple regions (Canada, EU, UK), we enhanced the Evidence Summary by making it include information about recipients’ attempts to authenticate themselves via ID Verification.

Bug Fixes

Senders

• PB-92738: Fixed an issue in which an invitation email failed to be sent because the recipient’s email address contained an ampersand (&). To fix this problem, if a Sender enters an address with an ampersand, an Invalid Email Address message will now appear. Senders will thus be blocked from using addresses that contain an ampersand.
• PB-93911: Fixed an issue in which Bulk Sending failed when Mutual TLS authentication (mTLS) was configured for the account.
• PB-94226: Fixed an issue in which some required fields were not correctly labeled in the Designer;
• PB-93669: Fixed an issue in which a Sender was able to create a transaction without an expiry date, even though default and maximum expiry values had been set at the account level.
• PB-93660: Fixed an issue in which a Sender could not configure an unlimited expiry time for a transaction, even though the account-level settings allowed it.
• PB-90113: Fixed an issue in which trying to configure a transaction’s expiry time in the Designer triggered an error.
• PB-95000: Fixed the following issue on the Designer page. If a Sender clicked the Accept Only button before a document had finished loading, it triggered an error.
• PB-94199: Fixed the following issue that occurred during transaction creation. When a Sender used the Chrome browser's Auto-fill feature, the transaction’s correct name was replaced by pre-filled user information.
• PB-93616: Fixed an issue that arose in the following situation. (1) In BackOffice, the feature Allow Duplicate Signer Email Address was disabled. (2) In the Designer, a Sender tried to add a recipient to a transaction using an email address that was already in use by another recipient. (3) This triggered an error message. (4) The Sender responded by changing the new recipient’s email address to a unique address. (5) At this point, the system should have added the new recipient to the transaction. Instead, it displayed another error message.
• PB-93805: Fixed an issue in which the banner Start your first transaction failed to extend to the edge of the page.
• PB-92455: Fixed an issue in which the text in transactions' Status column wrapped across two lines, and the second line contained only the last character of the last word.
• PB-94736: Fixed the following issue. Sometimes when delegates accessed their delegators’ Dashboard, it failed to indicate that their signature was required on a transaction.
• PB-92675: Fixed an issue in which the Designer page became unresponsive when a Sender: (1) clicked and dragged a field to a new position; (2) did not let go of the left mouse button; (3) pressed the Delete key.
• PB-94734: Fixed an issue in which accessing a trashed transaction from the Sender part of the New User Experience triggered an error.
• PB-93348: Fixed the following issue. A transaction was created and sent, then interrupted (e.g., Edit Transaction), then sent again. Both signers and reviewers should then have received an email reminder about the transaction, but the reviewers did not.

Signer Experience

• PB-94787: Fixed an issue that occurred after a Sender rejected a signer’s attachment, and sent the signer a notification about this. When the signer opened the notification email and clicked View documents, it triggered an error.

• PB-95818: Fixed the following issue. After all signers have signed, and a signer refreshes their browser on the Summary page (aka the Thank You page), the system should redisplay that page. Instead, it displayed the last signed document.
• PB-93797: Fixed an issue in which the system failed to display a proper error message when an account Sender tried to access the Signer Experience for a transaction in which they were not a recipient.
• PB-94572: Fixed an issue in which Zoom controls disappeared from the More Actions menu when the browser window was re-sized to 800 x 950 pixels or smaller.

New User Experience

• PB-91832, PB-88911: Fixed an issue in which: (1) fields were added to a document via the Designer; (2) in the signed document, those fields appeared two pixels away from their assigned positions.

• PB-95822: Fixed an issue that arose when recipients began reviewing the documents of a completed transaction that did not contain an Electronic Consent document. The system should have responded by displaying the transaction’s first document, but instead displayed its last document.

Developers

• PB-95776: Fixed an issue in which a PUT call to reorder a transaction’s documents created a blank placeholder, which in turn caused an Unhandled Server Error.

• PB-94030: Fixed the following issue that occurred in a transaction created via the API. After the transaction was sent for signing, having included two successive backslashes (\\) in a recipient's name caused an Invalid JSON error.

Account Owners

• PB-88113: Fixed an issue in which an error was triggered when an Account Owner clicked Admin on the top menu, and then selected Senders.

Accessibility

• PB-93324: Fixed an issue in which a Screen Reader failed to introduce a Capture Signature panel.
• PB-93326: Fixed an issue in which a user could not TAB into the signature-drawing part of a Capture Signature panel.
• PB-94282: Fixed an issue in which transactions with Accessibility Mode enabled triggered DOCUMENT_NAVIGATION and DOCUMENT_VIEW events for each field accessed. Now: (1) a DOCUMENT_VIEW event is triggered only when a user has viewed a document; (2) a DOCUMENT_NAVIGATION event is triggered only when a user has navigated to a document.
• PB-92456: Fixed an issue in which, upon opening the modal window Resend SMS?, the accessibility focus was on the Resend button rather than the Close[X] button.

Remote Online Notarization

• PB-94037: Fixed an issue in which some iPhone devices failed to correctly display pages during a Remote Online Notarization session.
• PB-93708: Fixed an issue in which the Thank You page for notaries displayed an incorrect message.

Virtual Room

• PB-95729: Fixed an issue in which some elements in a Firefox browser were incorrectly highlighted during a Virtual Room session.

In-App Reporting

• PB-92028: Fixed an issue in which exporting a Transaction Report to a CSV file caused issues if a transaction's name contained a comma. Each such comma is now replaced by a space.

Audit Trail

• PB-93000: Fixed an issue in which the Audit Trail didn’t provide a reason why an ID Verification attempt had failed.

Changed Behavior

• PB-92849: We improved the Signer Experience's validation of date-picker fields. For example, the system now: (1) automatically prepends a "0" if a single-digit value is input for the day or month; (2) instantly rejects out-of-bounds values (e.g., "13" for the month). These improvements resulted from upgrading the MUI X front-end library. For more information, click here.
• PB-94397: We changed the labels of the following Notary fields within the Designer: (1) NotaryLicenseNumber became Notary Commission Number; (2) NotaryLicenseExpirationDate became Notary Commission Expiration Date.
• PB-92028: When a Transaction Report is exported to a CSV file, any comma in a data field is now replaced by a space.
• PB-92561: To prepare for Release 23.R4’s addition of new supported languages: (1) we changed the name of the existing English language to English (United States); (2) we changed the name of the existing Spanish language to Spanish (Latin America). Their associated language codes have not changed.
• PB-95100: To reflect OneSpan’s new colors, we rebranded: (1) the checkboxes in the Sender part of the New User Experience; (2) "selected" radio buttons in the Designer.

Upcoming Changes

• PB-95735: In Release 23.R4 (11.53)., the Signer Experience’s Session Timeout warning message will be modified to display the relevant number of hours.
• Starting in Release 23.R4 (11.53), OneSpan Sign will support only the latest stable version of its supported browsers (Chrome, Firefox, Edge, Safari). This will apply to both the Signer Experience and the Sender part of the New User Experience.
• PB-93756: Starting in Release 23.R5 (11.54), the format of all Date fields in exported CSV files will be "yyyy-MM-dd HH:mm:ss". This applies to the following CSV files: (1) Notary Journal Export; (2) Transaction Usage Report; (3) Transactions Scheduled Report; (4) Account Scheduled Report.

Known Issues

• PB-95735: A known issue is affecting the Signer Experience’s Session Timeout warning message. If the parameter "esl.login.session.timeout.warning" is set to a value higher than 59 minutes, that message fails to display the number of hours. For example, if that parameter is set to 1 hour 2 minutes (3720000 milliseconds), that message incorrectly states that the timeout will occur in 2 minutes (instead of 1 hour 2 minutes). This issue will be fixed in Release 23.R4 (11.53).

• PB-97194: In Self-Service Account Configuration, the transaction setting Allow document download for incomplete transactions currently works with "reversed logic" — i.e., the functionality is allowed when unchecked, and not allowed when checked. This issue will be fixed in Release 23.R4 (11.53).

• PB-96940: When a transaction is being created via the API, a 500 error is thrown if Allow Duplicate Signers is enabled and Allow Duplicate Signer Phone Number is disabled. This issue will be fixed in Release 23.R4 (11.53).

• PB-89508: The system setting Transaction expiry warning (days) is not functional via Self-Service Account Configuration. It will be removed in Release 23.R4 (11.53).

• PB-95581: The BackOffice feature Allow Duplicate Signer Phone Number currently doesn’t work with “internal signers” (i.e., Senders who are also signers). This issue will be fixed in a future release.

• PB-94961: In the Designer, when a Sender tries to Select a Layout or Show Shared Layouts, nothing appears in the list of layouts. This issue will be fixed in a future release.

SaaS 2023-June: Release 23.R2.1 (11.51.1)

This is a security patch release.

SaaS 2023-May: Release 23.R2 (11.51)

What's New

Remote Online Notarization

• Added ID Verification for RON: Remote Online Notarization now supports the ID Verification authentication method. During ID Verification, a picture of the signer’s ID is shown to the Notary so they can compare it with the signer’s video feed. Fields in the Notary’s Journal are changed to reflect the information that was used during ID Verification.
• Added KBA for RON: Remote Online Notarization now supports the KBA authentication method. This feature must be enabled separately for each account that wants to use it.
• Added a reminder to start recording: At the start of a Remote Online Notarization session, a note about recording the session is now displayed to the Notary.

Signer Experience

• Improved Capture Signature: The Capture Signature panel has been improved in the following ways: (1) the panel now displays the instruction Draw your signature; (2) the signature area now has a background color and a border; (3) signers can now maximize or minimize the panel. Note: Drawing a signature and then resizing the panel will clear the signature. This is expected behavior.
• Split Signature Box: To prevent overlaps among a signature, its timestamp, and its watermark logo, we enabled each of these elements to be displayed in a separate section of the Signature Box. Once enabled, this feature affects all signature types except Click-to-Initial. However, the feature is available only within new transactions.

Senders

• Can add fields not tied to a participant: Senders can now add to a document fields that are not associated with a particular recipient. After a transaction is sent, its participants can see such fields in documents, but they cannot edit them. Note: (1) the values of such fields can be configured only in the Designer; (2) this feature must be enabled either by contacting our Support Team, or by using the Account Setting self-service in the Sender part of the New User Experience; (3) in the Account Setting self-service, this feature is called Imprint fields.
• Conditional fields highlighted more often: In the Designer, fields to which conditional logic applies now display a conditional-logic icon even if the Sender is focusing on an unrelated field.
• Sender UI rebranded: We rebranded the OneSpan Sign logo and colors in the Sender part of the New User Experience.
• Can copy-paste multiple fields at once: In the Designer, Senders can now copy-paste multiple fields at once within the same document.
• Can delete multiple fields at once: In the Designer, Senders can now delete multiple fields at once within the same document.
• Better experience when trying to move fields between documents: Formerly, when a Sender tried to drag one or more fields from one document to another in the Designer, the fields were blocked at the document’s edge, but there was no indication as to why this was being done. Now: (1) a message at the border between the documents states that fields cannot be moved from one document to another; (2) the "blocked" document is grayed out.

Bug Fixes

Senders

• PB-88953: Fixed the following issue. When a Sender used the API to upload a file with an unsupported file name, the system should have displayed a validation error. Instead, it displayed an internal error.
• PB-90376: Fixed an issue in which the system failed to indicate that a transaction's language was the one configured when the transaction was created. This happened after the Sender added a recipient to the transaction from the Designer.
• PB-91545: Fixed an issue in which the Unlock Recipient button mistakenly appeared disabled for a recipient who had been assigned SMS authentication within an in-person transaction.
• PB-89371: Fixed an issue in which an error was triggered when a Sender tried to trash a transaction that had been created from a template with placeholder recipients. This occurred only when the Trash button was clicked from a page that had not been refreshed since the transaction was created.
• PB-90671: Fixed an issue that was causing document pages to be duplicated in the Designer’s Documents panel.
• PB-91637: Fixed a Designer issue in which fields appeared on documents to the left of their assigned positions.
• PB-92211: Fixed the following issue. A Sender used the Designer to: (1) create a transaction; (2) flag one of its recipients as Accept Only. The Sender should not then have been able to add fields to a document for this recipient. However, the Sender could do this. Note: This issue occurred only when the feature No Signature Fields was enabled in OneSpan Sign BackOffice.
• PB-91916: Fixed an issue that arose in the following situation. When a Sender resized a field in the Designer, they made the field extend outside the document (e.g., slightly above the top of the document). This action triggered the following error: Invalid position. Object placed outside of document page boundary. Now, the system performs the resizing without an error, and keeps the resized field within the document.
• PB-72091: Fixed an issue that caused the Designer to crash when Senders uploaded documents whose pages were smaller than letter size.
• PB-91876: Fixed an issue in which the Designer crashed after a Sender selected fields in different documents using Shift + Click.
• PB-91675: Fixed an issue in which the Designer’s Document Preview panel flickered until the application crashed.
• PB-91948: Fixed an issue in which fields on non-active documents in the Designer were not grayed out when fields on the active document were being dragged.
• PB-91122: Fixed an incorrect translation into Portuguese of text about the Bulk Send feature. The correction uses text provided by a native Portuguese speaker.
• PB-93008: Corrected a grammatical error in Japanese on the Transaction Details page.
• PB-92932: Fixed the following issue. A Sender: (1) created an account that had a sub-account; (2) added a user to the parent account, and assigned them a customized role; (3) created a new account, and migrated it under the sub-account. At that point, the existing user should still have had only its assigned customized role. Instead, the existing user had acquired the role of Sender.
• PB-90750: Added missing information in a warning message to Senders. Old Message: This document already contains signature fields. Setting the document as Accept Only will remove all the signatures and data fields that it currently contains. Do you want to continue? New Message: This document already contains signature fields. Setting the document as Accept Only will remove all the signatures and data fields that it currently contains tied to the selected recipient. Do you want to continue?

Signer Experience

• PB-93747: Fixed an issue that occurred when a signer with more than two names (e.g., First, Middle, Last) signed using their initials. The Initials box in the Signer Experience should have displayed all the signer's initials. Instead, it displayed only two.
• PB-91656: Fixed a Signer Experience issue in which a selected date could not be cleared from the Date field.
• PB-91114: Fixed the following issue. When a drop-down list or a Text Field with a height less than 20 pixels was added to a document, it moved down a few pixels after signing was complete.
• PB-91834: Fixed an issue in which a signer who had been assigned only optional signatures failed to receive an invitation email.

Accessibility

• PB-92110: Fixed an issue in which Screen Readers failed to detect Zoom In and Zoom Out buttons in the Signer Experience.
• PB-91405: Fixed the following issue. When users were being authenticated via SMS, Screen Readers failed to read error messages for an expired or incorrect SMS code.
• PB-92358: Fixed an issue in which iPhone users could not enable Accessibility Mode.
• PB-92213: Fixed the following issue. If a user enters a wrong answer when they are being authenticated, a banner notifies them that their response was incorrect . That’s also true in this issue. The problem was that the code accompanying the banner said: role="dialog". This could have confused the users of Screen Readers.

Remote Online Notarization

• PB-90461: Fixed an issue in which a CLEAR button on the Notary Commission dialog box or a Signature Field failed to localize when the language was changed.
• PB-90374: Fixed an issue in which a Notary who had been assigned an optional signature was prevented from confirming a user’s identity.
• PB-90445: Fixed an issue in which a Notary was wrongly listed as a signer when a Journal Entry was downloaded as a PDF.

Delegation

• PB-89895: Fixed the following issue. Before a document was confirmed, a signature failed to display the name of the delegate who applied the signature. Instead, it displayed the name of the original signer.
• PB-89825: Fixed an issue in which the Evidence Summary displayed the name of the original signer for some events, instead of the name of that signer's delegate.

In-App Reporting

• PB-89983: In the column titles of Spanish In-App Reports, we fixed some translation and letter-case issues.

Evidence Summary

• PB-90899: Fixed an issue in which a Downloaded Document entry was mistakenly duplicated in the Evidence Summary.
• PB-92402: Fixed an issue in which the size of Evidence Summary files in the Japanese language were too big (each file more than 8 MB).

Account Owners

• PB-92124: Fixed a broken link on the Account Configuration page.

Developers

• PB-94197: Fixed an issue that caused the sessions of customers using iFrames to expire prematurely. The problem was that the system was failing to fire iFrame Lifecycle Messages (aka iFrame JavaScript Events) in the correct order. To view an example of events fired in the correct order for a typical transaction, see the content under the table in the section Notification Event Types.

Changed Behavior

• PB-89197: By default, the Capture Signature panel now opens in a minimized window. Users can maximize the window if they wish.
• PB-91028: When a transaction’s last document is Accept Only, and the relevant recipient has accepted it (thus completing the transaction), that recipient is directed to the Thank You page. Refreshing that page now leaves the recipient on that page. It used to redirect the recipient to the last document.
• Please note that as of this release (23.R2), you are no longer able to request the activation of the sub-accounts feature. For customers currently using sub-accounts, incidents related to undocumented use cases will be lowered to priority P3 or P4. For priority P1 or P2 incidents related to sub-accounts, we will use commercially reasonable efforts to provide workaround solutions if: (1) the account's use is being impacted operationally; (2) the customer cannot find a root cause of that impact within their own systems; and (3) we determine that a solution for the incident does not require new code. We made this decision to focus on creating enhanced account-management features that will result from an integration with our new OneSpan Transaction Cloud Platform. Please note that you can still request the creation of new OneSpan Sign accounts, and obtain help from our Support Team to configure your accounts.

• PB-89265: We improved the performance of the Signer Experience by modifying the rules that govern the fetching of documents. In particular, in some situations the system will fetch an original PDF instead of a flattened PDF. Fetching an original PDF is faster because it’s stored in cache memory, whereas a flattened PDF is always regenerated when it’s fetched.

  The following paragraphs describe further details.

Flattened PDFs: Flattened PDFs will be fetched for only the following activities: (1) viewing a signed document whose signatures have been confirmed; (2) viewing an Accept-only document after it has been accepted; (3) viewing a document that was signed or accepted by another recipient before the current recipient accessed the transaction.

Original PDFs: Original PDFs will be fetched for all these activities: (1) accessing a document (regardless of whether it has been designated for signing, Review-only or Accept-only); (2) viewing a signed document whose signatures have not been confirmed; (3) viewing an Electronic Consent document; (4) viewing a Review-Only document; (5) viewing a document for which: (a) the current recipient has completed all their actions; (b) another recipient still has pending actions (sign or accept).

Note: As we implemented these changes, we made efforts to preserve callback integrity – i.e., to ensure that customers’ callback integrations will continue to work without modification.

Known Issues

• PB-88685: An error may sometimes appear when changes on the Account Configuration page are saved. If this occurs, refresh the page and try again. This issue will be resolved in a future release.
• PB-91040: When a delegate tries to sign using a signature type other than Click-to-Sign, they may encounter a 403 error. This issue will be resolved in a future release.
• It may require up to 2 minutes for changes on the Account Configuration page to take effect.

SaaS 2023-April: Release 23.R1.2 (11.50.2)

This release applies only to the environments Canada Sandbox and Canada Production.

Bug Fixes

• PB-93974: Fixed an issue that occurred within an iFrame signing session that had been created using a Signer Authentication Token. The problem was that when a signer confirmed a document they had finished signing, an Unauthorized Access error message appeared.

SaaS 2023-March: Release 23.R1.1 (11.50.1)

This release applies only to the environments Canada Sandbox and Canada Production.

Bug Fixes

• PB-93389: Fixed an issue in which event notifications were incorrectly triggered from an iFrame.

Known Issues

• PB-86851: An additional View event may appear in the Evidence Summary after a document has been confirmed.

SaaS 2023-March: Release 23.R1 (11.50)

What's New

OneSpan Notary (Remote Online Notarization)

• Introducing OneSpan Notary: OneSpan Notary enables both Remote Online Notarizations (RON) and in-person notarizations. The RON functionality enables a Notary and signers to join a remote online notary session in which the Notary: (1) acts as the session’s host; (2) permits users to sign documents; (3) confirms the signed documents with a Digital Notary Seal.

This RON functionality introduces the following new features: (1) Notary Commission; (2) eJournal; (3) a transaction type called Remote Online Notarization.

From the point of view of OneSpan Sign, a “Notary” is a Sender who has either been granted "Notary rights"., or who has been assigned the role Notary.

Once a Sender is a Notary in that sense, they must configure a “Notary Commission” by: (1) clicking My Account > Notary Commission; (2) providing commission information in the dialog box that appears.

When a Sender creates a remote online notary transaction, they must specify: (1) a valid Notary for the transaction; (2) a date and time for the transaction's signing session.

After the Notary enters a remote online notary session, they must confirm each signer’s identity. For this initial release, the only supported authentication method is that the Notary knows the signer personally.

A remote online notary session follows the same rules as a Virtual Room session.

After all documents have been signed by the signers and the Notary, the Notary can end the remote notarization session. The Notary will then be redirected to an eJournal. This is an electronic log in which the Notary must record information related to their notarization. The journal can be downloaded from the My Account > Journal link in the Sender part of the New User Experience.

For this initial release, only the following notary jurisdictions are supported: (1) Alaska; (2) Arizona; (3) Hawaii; (4) Minnesota; (5) Ohio; (6) Oklahoma; (7) Tennessee; (8) Texas; (9) Virginia; (10) Washington.

To enable OneSpan Notary, please contact our Sales Team.

Rebranding

• Rebranded OneSpan Sign with new colors & logo: We've updated: (1) the logo and colors in the Electronic Consent document; (2) the watermark signing logo; (3) the logo in the Evidence Summary; (4) the colors in email templates.

Senders

• Added transaction descriptions to transaction names: In the Sender part of the New User Experience, transaction descriptions now appear in any list or table that contains transaction names. These descriptions appear directly under the names, but use a smaller font. This will enable Senders to differentiate transactions that have the same name.
• A document can be signed by some, and accepted by others: Formerly, Senders could assign only one of the following states to a transaction's document: (1) Signable; (2) Accept-Only. The assigned state applied to all transaction recipients. Senders now have the option of assigning another state to a document. The new state requires a document to be: (1) signed by some recipients; (2) accepted by other recipients. Note: The Transaction Owner (aka "Myself") cannot accept documents.
• Can reposition multiple fields at once: Formerly, the multiple selection of fields within the Designer could be used only to align fields. Now, this multi-select functionality can also be used to reposition multiple fields at once within the same document. This will enable some transactions to be created faster.
• ID Verification supports same email address: A transaction that uses ID Verification can now accommodate signers who have the same email address.

Developers

• Added Document ID & Recipient ID to the Audit API: The Document ID and Recipient ID are now in the JSON returned by the call api/packages/<packageId>/audit. This information will enable developers to: (1) differentiate documents that have the same name; (2) differentiate recipients who have the same name. Note: The Recipient ID is not tracked for ID Verification events.

Bug Fixes

User Authentication

• PB-87150: Fixed an issue concerning repeated authentication attempts via ID Verification's configuration called Document Verification Only. The system should have allowed only three failed attempts, but it allowed four.
• PB-87989: Fixed the following issue. If a user employed a Signer Authentication Token to access the Signer Experience, the system failed to display its customized message for unauthorized OFAC access.

Signer Experience

• PB-90661: Fixed an issue in which a signer who had just completed all their actions on a transaction was presented with the misleading message: Currently not your turn to sign.
• PB-89223: Fixed an issue that arose in the left pane of the Signer Experience. The problem was that the word DOCUMENTS overlapped the number of documents, and the word UPLOADS overlapped the number of uploads.
• PB-87913: Fixed an issue in which the Signer Experience's left pane displayed a document’s status as Signing completed, though the document still required actions.
• PB-91298: Fixed a rare race condition that caused the text entered by a signer in a Text Area field not to appear in the document after the signer: (1) signed the document; (2) reopened the document.
• PB-91711: Fixed an issue in which some Autofields were not getting populated if multiple signers had an Autofield with the same name.

Senders

• PB-85790: Fixed an issue in which a Sender opened an expired transaction from the Drafts tab, and then resent it. The problem was that the system failed to resend the transaction.
• PB-89092: Fixed an issue in which a transaction failed to be sent as expected. The root cause was that the transaction had been created from a template that used conditional logic on a field that no longer existed.
• PB-87718: Fixed an issue in which it was possible to configure a transaction expiry date that exceeded the Designer’s maximum number of days before expiration.
• PB-89186: Fixed an issue in which a user logged in to a Free Trial account, and then changed the language from the top-right menu. The problem was that the system failed to change the language of the Free Trial banner.
• PB-76319: Fixed the following issue. By clicking the Org Accounts icon on the Dashboard, Senders viewed sub-accounts that they should not have been able to view. These were sub-accounts in which the Senders had no Role.
• PB-83290: Fixed an issue in which sub-accounts failed to inherit the “theme” (e.g., branding colors) configured in the Sender part of the New User Experience.

New User Experience

• PB-87999: Fixed an issue in which some text within PDFs was not rendering properly in the New User Experience. The issue affected both the Signer Experience and senders (e.g., the Designer). Note: This issue has been fixed for most use cases. However, it may still occur when specific hardware configurations are used with unconventional PDF documents. We will continue to monitor PDF.js documentation for any resolution.

Developers

• PB-87868: Fixed the following issue. If OneSpan Sign BackOffice is used to change the value of the parameter email.from in the resource email.properties, the FROM email address in an email template's JSON should be updated automatically. The problem was that this update didn’t happen.
• PB-88857: Fixed an issue in which the system failed to translate a parameter of the email template email.bulk.send.completed.

Virtual Room

• PB-89453: Fixed an issue in which the Get started button was not visible to signers in a Virtual Room session if they were on a mobile device.
• PB-89410: Fixed the following issue that arose during a Virtual Room session. When a signer repeatedly clicked the Signature Navigator’s Next button, the system iterated through the required fields of all the session’s participants. It should have iterated through only the required fields of the current signer.
• PB-89278: Fixed an issue that arose during a Virtual Room session. The problem was that the system displayed an empty space in a signer's list of attachments.
• PB-87215: Fixed an issue in which: (1) a participant joined a Virtual Room session after the session had started; (2) the system failed to inform the participant that a recording of the session was already in progress.

Delegation

• PB-88863: Fixed an issue in which the delegation feature failed in sub-accounts.

Evidence Summary

• PB-86851: Fixed an issue in which the Evidence Summary recorded that a Confirm Signatures event was followed by a View event. The problem was that the View event never occurred.

Accessibility

• PB-89715: Fixed an issue in which Screen Readers failed to correctly read conditional logic that appeared in the Designer.
• PB-91835, PB-91405: Fixed an issue in which Screen Readers on desktop or mobile devices failed to read error messages about invalid or expired SMS passcodes.

Changed Behavior

• PB-88352: Within the Data Retention dialog box, we've changed how an Unlimited retention period is configured. A checkbox has been added.
• PB-89362: If the Incomplete Evidence Summary feature is enabled for an account, that account’s Senders can now download the Evidence Summary no matter what state the transaction is in (including Draft).
• PB-87819: The system will no longer display the popup window that was formerly used to identify recipients as acceptors or reviewers. Instead: (1) to make a recipient an acceptor, the transaction creator can merely select the Accept Only checkbox for that recipient; (2) to make a recipient a reviewer, the transaction creator can just: (a) leave the Accept Only checkbox clear for that recipient; (b) not add any fields to the document for that recipient.
• PB-86346: Before signing is complete, Initials fields used to show the signer’s full name. Such fields now show just the signer’s initials (as they will appear in the flattened – i.e., completed – view of the document).
• PB-88409: This change concerns the Signer Experience message which warns signers that their session will soon expire. Formerly, the time left before expiration was expressed as a decimal number (e.g., 4.83 minutes). That time is now expressed as whole numbers of minutes and seconds (e.g., 4 minutes and 50 seconds). The new format is more human-friendly.

Upcoming Changes

• As part of our Rebranding initiative, we will update the watermark logo that appears in signed Signature Blocks.

• As of Release 23.R2 (11.51), you will not be able to activate Enterprise Administration’s sub-accounts feature. For customers who are currently using sub-accounts, incidents related to undocumented use cases will be lowered to priority P3 or P4. For priority P1 or P2 incidents related to sub-accounts, we will use commercially reasonable efforts to provide workaround solutions if: (1) the account's use is being impacted operationally; (2) the customer cannot find a root cause of that impact within their own systems; (3) we determine that a solution for the incident does not require new code. We made this decision to focus on creating enhanced account-management features that can be achieved by integrating OneSpan Sign with our new OneSpan Transaction Cloud Platform. Note: In Release 23.R2, customers will still be able to: (1) request the creation of new accounts; (2) obtain help from our Support Team to configure their accounts.

• PB-89265: Release 23.R2 (11.51) will improve the performance of the Signer Experience by modifying the rules that govern the fetching of documents. In particular, in some situations the system will fetch an original PDF instead of a flattened PDF. Fetching an original PDF is faster because it’s stored in cache memory, whereas a flattened PDF is always regenerated when it’s fetched.

  The following paragraphs describe further details.

Flattened PDFs: Flattened PDFs will be fetched for only the following activities: (1) viewing a signed document whose signatures have been confirmed; (2) viewing an Accept-only document after it has been accepted; (3) viewing a document that was signed or accepted by another recipient before the current recipient accessed the transaction.

Original PDFs: Original PDFs will be fetched for all these activities: (1) accessing a document (regardless of whether it has been designated for signing, Review-only or Accept-only); (2) viewing a signed document whose signatures have not been confirmed; (3) viewing an Electronic Consent document; (4) viewing a Review-Only document; (5) viewing a document for which: (a) the current recipient has completed all their actions; (b) another recipient still has pending actions (sign or accept).

Note: As we implemented these changes, we made efforts to preserve callback integrity – i.e., to ensure that customers’ callback integrations will continue to work without modification.

SaaS 2023-Feb: Release 22.R4.1 (11.49.1)

Bug Fixes

• PB-91114: Fixed an issue in which drop-down fields and Text Fields appeared displaced from their original positions during and after signing.
• PB-91242: Fixed an issue in which text in the Text Area of a signed document unexpectedly wrapped to a new line.

SaaS 2023-Jan: Release 22.R4 (11.49)

What's New

Free Trial

• Free Trial of OneSpan Sign: People who are not yet customers can now try our world-class e-signature solution for FREE. The trial lasts 30 days, and permits up to 100 transactions.

Senders

• Designer can configure fields numerically: In the Designer, a field’s position and dimensions can now be specified numerically. Using numerical values gives Senders more granular control over the fields they create. This functionality is in a new Layout section of the Designer's right pane.
• Easier to distinguish optional vs required fields: In the Designer: (1) optional fields now show with dashed borders; (2) required fields remain with solid borders. This will enable transaction creators to see if a field is optional or required without clicking on it to view its properties.
• Can easily identify default checkboxes and radio buttons: Before this release, the default value in a group of checkboxes or radio buttons was visually indistinguishable from the other objects in the group. Now, when a transaction creator slides the default value property to true for a particular checkbox or radio button, that object will appear in the Designer as "selected" (it will have a distinguishing checkmark or dot). Transaction creators can thus quickly identify the default value in such groups.
• Easier to select the right fields for conditional logic: When a Sender is configuring conditional logic, and is hovering their mouse over the list of added fields: (1) the Designer now highlights the field being hovered over; (2) a highlighted field is added to the logic when the Sender clicks it.
• Improved Keyboard Shortcuts menu: We improved the Designer's menu of keyboard shortcuts. Among other things, the list of available shortcut keys is now "OS-aware" — that is, it's customized to the user's Operating System (e.g., Mac, Windows).
• TimeStamps displayed instantly as users sign: Before this release, a timestamp appeared on an applied signature only after the signer confirmed it. Now, a timestamp can appear on an applied signature both before and after the signature is confirmed. This feature is disabled by default. To enable it, please contact our Support Team (or use Admin > Account Configuration > Transaction Settings > Signature Settings).

Developers

• Document Extraction supports Mobile Capture: Document Extraction now supports the Mobile Capture method of signing.

Bug Fixes

User Authentication

• PB-87103: Fixed an issue in which the area code 948 (Virginia, USA) was not recognized as valid when a recipient entered it as part of their phone number for SMS authentication.

Signer Experience

• PB-86077: Fixed an issue in which an inactive signer session expired later than the configured expiry time.
• PB-87900: Fixed an issue that concerned PDFs in which signing was complete. The problem was that certain iPhone models displayed these PDFs as blank documents.
• PB-85278: Fixed an issue that involved the following sequence of events. (1) A transaction's signing order was turned on. (2) The first signer began signing. (3) Before the first signer had finished signing, the second signer (who was also a Sender, but not the Transaction Owner) tried to accept an Accept Only document. (4) At this point, the system should have presented the second signer with the message: It's not your turn to sign. Instead, it presented them with an Access Denied screen.
• PB-87470: Fixed an issue that involved the following sequence of events: (1) a transaction was created via the API; (2) signatures were applied in Accessibility Mode. The problem was that the signatures were not visible when the transaction's documents were reviewed in Accessibility Mode.
• PB-87001: Fixed an issue that involved the following sequence of events. (1) Within the Signer Experience, a signer changed a document’s Zoom level to 175%. (2) The signer completed signing, and then reopened the document to review it. (3) The document’s magnification was still 175%, but the displayed Zoom level was 100% (the default value). The displayed Zoom level should have been 175%.
• PB-86693: Fixed an issue that involved the following sequence of events: (1) the feature No Signature Fields was enabled in OneSpan Sign BackOffice; (2) a Sender on the account added some required fields to a transaction’s document. The problem was that when a recipient accessed the transaction and viewed the document, the Signer Experience displayed the wrong number of required fields.

Senders

• PB-83788: Fixed an issue in which a transaction was cloned from a template that contained a signer with a required attachment. The problem was that the system failed to include the attachment in the new transaction.
• PB-87095: Fixed an issue in which the Designer’s vertical scroll bar became "stuck" behind page controls, and was therefore inaccessible. This occurred when the scroll bar became very small because a transaction had many pages or documents.
• PB-87556: Fixed an issue in which the ">" symbol in the Designer’s Recipients pane was misaligned.
• PB-88183: Removed a deprecated layout option (Display Save) from the Account Setting self-service.
• PB-88427: Fixed a grammatical error in the French text of the confirmation window for the action Send Transaction.
• PB-87877: Fixed an issue that involved the following sequence of events. (1) A Sender created a transaction with a document that included a Form Field with conditional logic and a Signature Block. (2) The Sender clicked the Clear All button, which removed the Form Field and Signature Block. (3) The Sender added a new Signature Block, and sent the transaction. (4) At this point, the system should have sent the transaction without errors. Instead, it displayed the error message: The field specified in the conditional logic cannot be found.

Account Owners

• PB-87916: Fixed an issue that involved the following sequence of events. (1) An Account Owner opened the Manage Delegation dialog box. (2) The owner searched for a Sender, but entered invalid data in the search field. (3) No Senders matched the search criteria. (4) The owner closed and then reopened the Manage Delegation dialog box. (5) At this point, that box should have displayed a list of Senders. Instead, it displayed the error message: There are no senders that match the search criteria.

Developers

• PB-87992: Fixed an issue in which the API was used to create multiple roles with the same name. It should never be possible for multiple roles to have the same name.

Accessibility

• PB-88060: Fixed an issue that arose if the Account Setting self-service feature was enabled in OneSpan Sign BackOffice. Screen Readers then failed to properly vocalize links that opened a new window.
• PB-85832: Fixed an issue that involved the following sequence of events. (1) A Sender assigned the KBA authentication method to the recipient of an accessible transaction. (2) The recipient used a Chrome or Edge browser to access the transaction. (3) On the KBA login page, the recipient failed to answer all questions correctly. (4) The system displayed a suitable error message at the top of page. At this point, the focus should automatically have moved to the top of page. Instead, it scrolled down slightly.
• PB-86541: Fixed an issue in which NVDA Screen Readers failed to read the banner beside the Accept button.
• PB-86787: Fixed the following issue. When a user focused on the input field that displays the message "Value must be greater than 0", JAWS Screen Readers vocalized the message five times. They should have vocalized the message just once.
• PB-87162: Fixed an issue that involved the Signer Experience panel used to upload attachments. The problem was that VoiceOver Screen Readers didn’t read the buttons Next upload and Go to documents separately. Instead, when a user focused on one of these buttons, the Screen Reader read a message that covered both buttons.

In-App Reporting

• PB-89179: Fixed the following issue. When a user tried to download multiple In-App Reports, the system delivered a zip file that was empty.

Evidence Summary

• PB-87529: Fixed an issue that arose when a PDF of the Evidence Summary was exported to a text file. The problem was that sometimes the text file contained errors (e.g., rogue characters).

Vulnerabilities

• PB-76750: We removed an unused component that had formerly been used by our Fast Track feature. Removing that component eliminated potential attack vectors.
• PB-87735: In the emails that OneSpan Sign sends recipients, we now escape/sanitize all email variables except $PACKAGE_MESSAGE and the email's Subject line. We've done this to prevent harmful links from being included in recipient-facing emails.

Changed Behavior

• PB-87925: Before this release, we verified user-entered area codes against a Phone Number Validation Library. Because this library was seldom updated, our system often flagged new area codes as invalid. To prevent this, we now verify area codes in a more relaxed manner by simply checking their number of digits.
• PB-88184: Within the Account Setting self-service, the string "Package Settings" has been renamed "Transaction Settings".

Known Issues

• PB-87999, PB-86583: Some text within documents may appear 'broken' or 'pixelated' For example, customers using machines equipped with Intel Iris XE integrated GPU are experiencing these rendering issues when they view PDFs on Chromium-based browsers (Chrome, Edge).
• PB-89742: Browsers on iOS 16+ have issues displaying any document whose contents are almost exclusively images (e.g., a PDF generated from a PowerPoint document). This problem is due to changes in the latest iOS 16+ version, so it will need to be resolved by Apple Inc.

Upcoming Changes

• Beginning with Release 23.R1 (11.50): (1) Microsoft Windows 8 and Microsoft Windows 8.1 will no longer be supported; (2) Microsoft Windows 11 will be supported. For more information, see Minimum Software Requirements.

SaaS 2022-Nov: Release 22.R3.2 (11.48.2)

Enhancement

• PB-89253: To accommodate the increased load expected for Black Friday, we have optimized how the system uses memory.

SaaS 2022-Nov: Release 22.R3.1 (11.48.1)

Bug Fixes

Senders

• PB-88732: Fixed an issue in which trying to access or search for certain transactions or templates triggered an error.
• PB-88510, PB-83320: Fixed an issue in which the Sender interface intermittently displayed a blank Login page.
• PB-88845: Fixed an issue that arose when a transaction was created from a template. The problem was that when a placeholder recipient was replaced, the system changed the recipient’s role (e.g., Signer1 became Signer3).
• PB-88904: Fixed an issue involving templates and transactions created from templates. Each of the following actions sometimes triggered an error: (1) navigating to the Designer page; (2) previewing a document via the Web UI’s Preview icon.

Virtual Room

• PB-88850: Fixed an issue in which trying to open a Virtual Room session within an iFrame triggered an error.

eOriginal

• PB-88903: Fixed an issue in which documents deposited in eOriginal vaults had a watermark that was too opaque.

SaaS 2022-Oct: Release 22.R3 (11.48)

What's New

Classic Signing Ceremony

• Classic Signing Ceremony is fully deprecated: The deprecation of the Classic Signing Ceremony began in Release 11.42. That ceremony's API endpoints have now been deactivated, so integrated users MUST now use the API of the Signer Experience. The Classic Signing Ceremony is now FULLY deprecated.

Signer Experience

• Better Electronic Consent workflow: When Change Signer is used, both the original signer and the reassigned signer must now accept the Electronic Consent document. The only exceptions are users who sign via the Personal Certificate Client or a Trust Service Provider. In those cases: (1) if the original signer accepts the Electronic Consent document before changing signers, the reassigned signer will not see that document; (2) otherwise, the reassigned signer will see that document, and must accept it.

• Better workflow for pending signatures: When a Sender is also a signer who has a pending signature in a transaction, a Sign icon now appears next to the name of the transaction. Clicking that icon brings the Sender directly into the Signer Experience for that transaction.

• Can view full document name on each page: When a document is viewed in the Signer Experience, its name appears at the bottom of each page. When a long name exceeds its allocated space there, the name is truncated with an ellipsis. Thus the last part of such names is not displayed. We have mitigated this limitation by showing the full document name when users hover their mouse over the truncated name.

• Can add watermarks to downloaded documents: If a recipient downloads a transaction's documents during the Signer Experience, those documents can be stamped with a customizable watermark that indicates the state of the transaction. The watermark's font, opacity, and position are also customizable. To enable this feature, please contact our Support Team.

Senders

• Can override recipients' language specifications: It’s sometimes useful for a Sender to be able to specify the language of the emails and User Interface that a transaction’s recipients will see, even if the recipients have specified other languages. We’ve therefore created a new account-level flag in OneSpan Sign BackOffice and the self-serve settings for Senders. If that flag is enabled, an account’s Sender can specify a transaction's “recipient language” that will override the recipients’ language specifications. Note: This feature is supported in the New User Experience and the API.

• Can add fields before Signature Blocks: After selecting a recipient, Senders can now add fields to a document without having added a Signature Block. Once a Signature Block is added, all previously added fields will be attached to it. Note: (1) The fields in question are Form-Building Fields (e.g., Text Fields, Text Areas, checkboxes, radio buttons, drop-down lists, labels); (2) This feature is supported in the New User Experience and the API.

• Bulk Send can use large templates: The Bulk Send feature can now accommodate templates that have 300 fields.

• More control over the "next document" button: Before this release, the button that takes a recipient to the next document during the Signer Experience might appear anywhere on a page of the current document. To enable more predictability, we’ve created a new account-level flag in OneSpan Sign BackOffice. When that flag is enabled: (1) that button always appears at the bottom of the page; (2) the button’s text can be customized using BackOffice.

• Easier to deselect delegates: A delegator can now easily stop the delegation of any of their delegates via the Manage Delegation dialog box, which: (1) lists all the delegator’s delegates; (2) displays a Stop Management button that will stop the delegation of a selected delegate.

Account Owners & Managers

• “Account Setting self-service” enabled by default: For all OneSpan Sign accounts (except those created or updated on OneSpan Sign 11.46.x or 11.47.x), Account Setting self-service is now enabled by default for Account Owners and Account Managers. This enables them to immediately configure many BackOffice settings directly from the Sender part of the New User Experience (under Admin > Account Configuration).

Evidence Summary

• Evidence Summary records IP addresses from ID Verification: As a user’s identify is being authenticated via ID Verification, their device’s IP address changes. Starting with this release, the Evidence Summary records those addresses.
• Better button labels: Before this release, the label for the button that downloads the Evidence Summary was causing confusion in some supported languages. For example, in French it resulted in two buttons with different functions presenting the same label – Télécharger (Download). We removed this confusion by ensuring that the button that downloads the Evidence Summary presents a unique label in every supported language.

Virtual Room

• Better video feeds: We increased the size of the Virtual Room's video feed to make it more visible. We also ensured that the system presents only one video feed per participant – i.e., we no longer duplicate the video feed for the person controlling the screen.

• Can select hosts from the Designer: From within the Designer, a Sender can now: (1) select the host of a Virtual Room transaction; (2) send the transaction to its participants. Formerly, if a Sender was in the Designer, they needed to return to the Transaction Edit page to do these things.

Accessibility

• “Account Setting self-service” is accessible: Account Setting self-service is now accessible, so people with disabilities can configure many BackOffice settings directly from the Sender part of the New User Experience (under Admin > Account Configuration).

• Better handling of fields in groups: When fields in a Checkbox Group or a Radio Button Group are added to a document in an Accessibility Enabled transaction, the drop-down list now displays the group name. Users must therefore add the entire group. They can’t add only some of the group’s fields. Similarly, when fields in a group are removed from a document, the entire group is removed.

• Autofields are more readable: We enhanced the readability of pre-filled text in the autofields imported to an accessible transaction’s PDFs.

Bug Fixes

Signer Experience

• PB-85685: Fixed an issue in which confirming a signature triggered a validation error.

• PB-86368: Fixed an issue in which the Download ALL command failed. Such failures occurred because two or more documents had the same name. That situation no longer causes an issue.

• PB-86420: Fixed an issue in which a template with conditional logic shared with other accounts could lead to the following error message when signing: Error: Signing order has been violated.

• PB-85651: Fixed an issue in which the system failed to send a SIGNER_COMPLETE event notification for a transaction after all its required signatures had been applied.

• PB-85044: Fixed an issue regarding signing on mobile devices. The problem was that signers were able to click the Done button before they added a Mobile Signature. This resulted in the system wrongly indicating that a signature had been applied.

• PB-84646: Fixed an issue in which users with no Signature Fields in a document were nonetheless on the list of users “required to sign” the document.

• PB-83078: Fixed the following issue. The Accept banner (prompt + button) for the Electronic Consent document should have appeared at the bottom of the document. Instead, it "floated" at the bottom of the screen.

• PB-84199: Fixed an issue in which the Signature Navigator’s Next button skipped over a required Checkbox Group.

• PB-80908: Fixed an in-person transaction issue in which: (1) Signing Order was turned on; (2) the Transaction Owner was the first signer (3) the next signer couldn’t access the transaction until they refreshed the page.

• PB-85526: Fixed an issue in which the left-pane Navigation Menu failed to open automatically on touch-screen devices.

• PB-87863: Fixed an issue in which an inactive signer session expired earlier than the configured expiry time.

• PB-86027: Fixed the following issue. When a signer clicks the link in their invitation email after the associated transaction has been completed, they should be redirected to the Thank You page. Instead, they were redirected to the Overview page.

• PB-86611: Fixed the following issue. A user signed all their required Signature Fields in a transaction, but subsequently declined the transaction when viewing the transaction's last document, which had no signatures/approvals for the user. At that point, the system presented the user with the following contradictory messages: (1) Please view attached image (decline.png); (2) The transaction has been successfully completed.

Senders

• PB-83421: Fixed an issue in which Bulk Sending operations based on a template failed because the system miscalculated the template’s expiration date.

• PB-80750: Addressed an issue in which the system’s email to a Sender failed to include an attachment containing the Evidence Summary and all signed documents. Now when the attachment’s size is more than 7 MB: (1) this type of email will not include the attachment; (2) the Sender can view the transaction’s documents by clicking a link in the email.

• PB-82852: Fixed an issue in which a 400 error was thrown when an accessible transaction was being created with Text Anchor extraction.

• PB-85547: Fixed an issue in which an error arose when a layout with conditional fields was applied to a transaction with fewer documents and fields.

• PB-84954: Fixed an issue in which removing a signer from a transaction failed to remove the conditional logic related to them. This led to an Unhandled Server Error during signing.

• PB-84692: Fixed an incorrect German translation of text about the Signing Order.

• PB-83151: Fixed the following issue. An error was triggered when a Sender used a Firefox browser to add a Signature Field for a recipient in an accessible transaction.

• PB-82888: Fixed the following issue. When the Designer page was viewed in Chromium/Edge browsers, it was missing the "3 dots" that enable the Documents tab to be opened.

• PB-84990: Fixed the following issue. In a Word document’s embedded creation date, the month was spelled entirely in lower-case letters. When the document was uploaded to a OneSpan Sign transaction, it was converted into a PDF. The problem was that the first letter of the month's name in the PDF was upper-case (e.g., april became April).

• PB-86492, PB-86583: Fixed an issue with the rendering of PDF documents within the application (WebUI). This issue was affecting all browsers.

• PB-85034: Fixed the following issue. When users accessed the Manage Delegation screen on a mobile device, long email addresses on that screen failed to display properly.

• PB-83439: Fixed an issue in which bounced email was recorded as a bounce not just for the email address in the To field, but also for the email address in Cc field.

Admins

• PB-83520: Fixed an issue that was preventing the deletion of roles from sub-accounts.

• PB-74822: Fixed an issue that arose when a role in a sub-account was assigned the permission Transaction visibility for delegates, but the parent account had no assigned roles or permissions. In this situation, the system wrongly allowed users without permissions to view the Transactions and Templates tabs.

• PB-83936: Fixed the following issue. When a transaction’s JSON was viewed in OneSpan Sign BackOffice, it contained no page attributes.

New User Experience

• PB-84926: Fixed an issue in which the Help option appeared in the More Options menu on the User Authentication page, despite the fact that the account-level flag showNseHelp was false.

• PB-84289: Fixed a misleading error message that appeared when users who were required to log in via SSO tried to reset their password.

• PB-85442: Fixed an issue in which the button Skip to main content didn’t work.

• PB-85501: Fixed issues with translations into Chinese (Traditional and Simplified).

Accessibility

• PB-70939: Fixed the following issue. WCAG 2.1 requires that the aria-label of a link or control must begin with the associated visual label. This requirement was not fully met.

• PB-85782: Fixed an accessibility issue regarding font legibility in the Signer Experience.

• PB-83921, PB-83996, PB-83919, PB-83808, PB-83676, PB-83365, PB-81732: Fixed seven issues involving accessible transactions.

• PB-81576: Fixed the following issue involving an accessible transaction. After a signer left the Exit Signing Mode banner, the system focused on the wrong part of the screen.

• PB-81571: Fixed the following issue. After clicking the Enable accessibility mode button, the focus automatically and wrongly moved to the Accept button.

• PB-81562: Fixed the following issue. After a user clicked a Sign button, the Screen Reader failed to provide feedback.

In-App Reporting

• PB-79325: Fixed an issue in which the filename of a transaction report changed from “Transaction_Report_2021_11.csv” before it was downloaded to "___________2021_11.csv" after it was downloaded.

• PB-86024: Fixed an issue with retrieving the filename of an In-App Report via the API. The API input parameter fileName (with an upper-case “N”) did not work, so we changed the code to make it work.

Callbacks

• PB-86972: Fixed an issue in which the system was not forwarding PACKAGE_DECLINED message strings to the Salesforce OAuth2 callback service. Now such messages are always forwarded.

• PB-81969: Fixed the following issue that arose when the signer is also aOneSpan Sign Sender – a Callback Notification recorded the wrong ID in the sessionUser field.

Vaulting

• PB-80732: Fixed an issue that was preventing documents from being registered via OneSpan’s e-Vault Manager Console.

Technology Updates

• PB-85399: Before this release, OneSpan Sign used a Windows-based program to convert documents from one file format to another. To improve font substitutions, OneSpan Sign will now use a Linux-based converter for all supported languages. Note: Some fonts may convert differently in OneSpan Sign 11.48 than they did in OneSpan Sign 11.47.

Known Issues

• PB-85089: Within the New User Experience, we are hiding the permission Manage users' transactions, templates, layouts (API). New clients will never see this permission. If a Sender has this permission today: (1) they can continue to use it; (2) they will no longer be able to see in the New User Experience if they or any other Sender has this permission. If a client wants to enable or disable this permission for a Sender, they must contact our Support Team.

• PB-89179: When an authorized user tries to download multiple In-App Reports, the download is delivered as a zipped file. That file should contain those reports, but instead is empty. The workaround is to download each report individually. This issue will be resolved in Release 22.R4 (11.49).

• PB-86077: An inactive signer session takes longer to expire than the configured time if that time is more than 1800000 ms (30 minutes). This issue will be resolved in Release 22.R4 (11.49).

SaaS 2022-Sep: Release 11.47.1

Bug Fixes

• MAIN-6746: Fixed an issue in which OneSpan Sign calls were failing in Production environments. In particular, a race condition sometimes triggered the following HTTP 500 error message: Unable to acquire JDBC Connection.

• PB-85688: We reverted the fix for this issue. That fix is described below in the Release Notes for OneSpan Sign 11.47.

SaaS 2022-Aug: Release 11.47

What's New

Senders

• Can create standalone co-browsing sessions: When this new feature is enabled on a transaction, a signer can ask the sender to arrange a co-browsing session for the transaction. The signer must provide their telephone number and preferred contact time, and they may add a comment. The API then transmits this information to the sender via an event notification. The sender can then arrange a co-browsing session with the signer. Note: (1) This is a paid feature. To purchase it, please contact our Sales Team. (2) This feature must be activated for your account. To activate it, please contact our Support Team.
• Standalone co-browsing requests have timezone labels: When a recipient makes a standalone co-browsing request, a timezone now appears for each "possible callback time" they select. Timezones are also displayed to the sender and other recipients of the transaction. Providing all participants with this information avoids misunderstandings about when the co-browsing session will take place.
• Can configure many BackOffice settings: Before this release, many Account, Feature, Package and Signing settings had to be configured by our Support Team, using OneSpan Sign BackOffice. Senders can now configure these settings directly from the Sender part of the New User Experience. Note: (1) These "self-serve" settings include most of BackOffice's Account, Feature, Package and Signing settings that are Boolean and non-paid. (2) Senders can access these self-serve settings under Admin > Account Configuration. (3) This feature is enabled by default for Account Owners and Account Managers. To change this feature's configuration, please contact our Support Team.
• Improved guidance on ID Verification: We improved our guidance to senders on how to configure ID Verification. In particular, senders now see the following message: The First Name and Last Name that you enter for the recipient must match those that appear on the ID document that the recipient will upload for ID Verification.

Signer Experience

• External signers can have same name and email: Different external signers can now have the same first name, last name and email address. This possibility was developed to accommodate those rare cases in which relatives or spouses share the same name and email address. This option is disabled by default. It can be enabled by our Support Team using BackOffice, or by Senders using their Account Configuration page. Note: "External signers" are signers who do not have an email account attached to a Sender or other OneSpan Sign role. This feature applies only to external signers.

Accessibility

• Enhanced zoom buttons: Formerly, tooltips for the zoom buttons in the Signer Experience did not specify if the buttons zoom in/out of the current document, or in/out of the entire screen. That ambiguity has been removed, since those tooltips now say Zoom into the document and Zoom out of the document. In addition, the button that zooms in now supports higher magnifications (up to 400%).

Evidence Summary

• Transaction status more visible: A transaction's Evidence Summary now records the transaction's status.

SMART Docs

• SMART Doc Audit Trail logs 'unpopulated' events: The Audit Trail for SMART Docs now logs unpopulated events. This functionality was required for Freddie Mac to consider OneSpan an authorized vendor of the eClosing process.

Bug Fixes

Signer Experience

• PB-83384: Fixed the following issue. When trying to confirm signed documents (accessible or not), the Confirm button sometimes failed to respond when it was clicked. This occurred only if the name in one of the documents' Signature Fields contained a period (.).
• PB-74520: Fixed an issue in which signers encountered the error message "The field’s value is too long", even if only one character was entered in a Text Field. This issue occurred only when the associated transaction was prepared via the API or an SDK. It occurred because the system was misinterpreting the meaning of the values 0 and NULL for the maxLength property of Text Fields. Going forward, 0 and NULL will mean 4000, which is a Text Field’s maximum permissible value.
• PB-79425: Fixed the following issue. In an in-person transaction, the message "Please pass the controls back to the host of this transaction" was confusing when the host had just finished signing. We changed this message to "Click the button below to continue the transaction".
• PB-83007: Fixed an issue in which a signer using the Uanataca Trusted Service Provider could not apply multiple signatures to a transaction's multiple documents.
• PB-84021: Fixed an issue in which signing via the Uanataca Trusted Service Provider failed in the US1 Production environment.
• PB-81257: We had received some complaints about the legibility of placeholder text in the Signer Experience. We fixed this issue by increasing the font size and weight of that text.

Senders

• PB-79838: Fixed an issue that involved searching for a transaction by date in the sender part of the New User Experience. The sender entered a date in the From field, and then pressed TAB to place their cursor in the To field. The problem was that doing so cleared the sender's entry in the From field.
• PB-78637: Fixed an issue involving the tooltip for the info icon on the Designer page. After a user collapses a tooltip by pressing the ESCAPE key, they should be able to expand it again by pressing the ENTER key or the Spacebar. The problem was that after the user collapsed this tooltip, expanding it again required navigating away from the icon and then back to it.
• PB-82017: Fixed the following issue, which occurred when an account’s Roles and Permissions feature was enabled. A user encountered an "unauthorized access" error when they tried to access the Signer Experience as a sender via a Fast Track URL.
• PB-80511: Fixed the following issue, which occurred when an account’s Roles and Permissions feature was enabled. A user encountered an "unauthorized access" error when they tried to access the Signer Experience as a sender via an email link.
• PB-83688: Fixed an issue that arose when a signer repeatedly failed to authenticate themselves via ID Verification, and was locked out of a transaction. When the sender subsequently viewed that signer’s status in the New User Experience, they should have seen a “locked signer” icon. The sender could then interact with that icon to unlock the signer, and resend the transaction. The problem was that the icon was not appearing, so the signer could not be unlocked.

Developers

• PB-81184: Fixed the following issue that involved our Digital Mortgage and Digital Lending solutions. Once the effort to store a document in an e-Original vault suffered a non-recoverable error, no email notification was sent to the transaction sender. Senders now receive emails about such failures.

• PB-85688: Fixed the following issue. After the failure of a developer's request for a transaction, the system changed the transaction’s status from SENT to DRAFT.

• PB-85045: Fixed the following issue. Between the 11.45 and 11.46 releases of OneSpan Sign, a change caused the font size of text inserted via Field Injection to shrink. The 11.47 release has restored the functionality of the 11.45 release. As a side effect of this fix, when a signed document is viewed in the application after signing is complete, some content in a Text Area might appear to be truncated. Note that this rendering behavior in our application does not affect the associated PDF’s actual content. The PDF contains the full text content, which displays properly when the PDF is viewed in a standard PDF viewer. We recommend that any problematic templates or layouts created in the 11.46 release be: (1) edited to adjust the font size to the Text Area; (2) saved again.

User Authentication

• SAA-12609: Formerly, when a recipient was authenticating their identity via ID Verification, the following message appeared on the "Capture Image" page: If this page doesn't go away after you finish capturing your images, click NEXT. That message was wrong. It has now been replaced by the following message: If this page does not refresh after you have taken all requested pictures, click IMAGE CAPTURE COMPLETE.
• PB-80302: Fixed an issue in which a sender configured Q&A Authentication so that the answers typed by the recipient would be visible to the recipient. The problem was that the typed answers were masked.
• PB-79541: Fixed an issue in which the Phone Number page was displayed twice to a recipient during ID Verification.
• PB-85687: Fixed the following issue, which occurred when the following features were enabled for an account: (1) Roles and Permissions; (2) SAML; (3) Auto-Provisioning. A new user in the account was assigned Single Sign-On Authentication (SSO), and their third-party Identity Provider assigned them a specific role. When that user subsequently logged into OneSpan Sign for the first time via SSO, they should automatically have been assigned that role. The problem was that this didn’t happen.

In-App Reporting

• PB-82588: Fixed an issue in which downloaded Account Reports were empty. This issue occurred only in Sandbox environments.

• PB-77375: Fixed an issue in which the Download button for Transaction Reports failed when only one report was selected for download. A single report can now be downloaded.

• PB-85129: Fixed the following Transaction Reports issue. In rare cases, an erroneous value appeared in the Signer Status column (e.g., CURRENT_SIGNER or FUTURE_SIGNER appeared instead of COMPLETED).

Accessibility

• PB-80643: Fixed the following issue involving an accessible transaction. Upon signing, a signer encountered an error message which correctly reported that the signer had failed to interact with a required field. The problem was that the link in that message did not take the signer to the required field.

Audit Trail

• CAPA-111: Fixed a clock-synchronization issue that could cause events in an Audit Trail to appear out of order.

Performance

• PB-81784: Fixed an issue in which certain race conditions were causing deadlocks.

Technology Updates

• PB-78771: We have migrated the OneSpan Sign Document Converter from Windows Virtual Machines to Linux containers. For the next few releases, every environment will run two converters in parallel — one on a Windows VM, the other in a Linux container. The Windows VM will continue to convert documents, just as before. The Linux container will do "mock conversions" of the same documents, while simultaneously logging processing information in log files. This strategy will enable us to study those logs to determine when we should switch over to using Linux containers alone. TIP: We strongly recommend that during this evaluation period, customers embed in their documents any fonts that are not supported by OneSpan Sign. A list of the fonts supported by OneSpan Sign can be found in our Supported Fonts section. The procedure Using PDF/A Documents describes how to create a PDF with embedded fonts from a Word document.

• PB-84027: On October 1, 2022, Microsoft will begin removing the ability to use Basic Authentication in Exchange Online. OneSpan Sign relies on Microsoft Exchange to send outgoing email messages to signers. Accordingly, we have modified our code to enable its Java Mail library to use OAuth 2.0 token-based authorization. For more information, including a description of actions we advise you to take, click here.

Known Issues

• PB-83687: The following sequence of events has created an issue. (1) A transaction template is created that adds a placeholder recipient, and assigns that recipient ID Verification. (2) A sender creates a transaction from that template, but replaces ID Verification with SMS authentication for an actual recipient. (3) The sender adds KBA authentication for the recipient, and sends the transaction. When the recipient accesses the transaction, they should be assigned only two authentication methods (SMS, KBA). Instead, they’re assigned all three methods (ID Verification, SMS, KBA).

• PB-86988: When a transaction’s multiple documents are viewed in a Chrome browser, the second document has no Signature Blocks. This is due to a recent change in how Chrome manages cookies. Effective workarounds include: (1) using another supported browser (e.g., Firefox); (2) closing and reopening the Signer Experience. This issue will be fixed in an upcoming release.

• PB-83928: Swisscom AIS is failing to sign any document whose name contains one or more non-Latin characters. This impacts the following supported languages: Arabic, Greek, Japanese, Korean, Russian, Simplified Chinese, and Traditional Chinese.

• PB-86778: When a user searches for a transaction in the Sender part of the New User Experience, the system mistakenly returns no results. The workaround is to: (1) press Clear; (2) search again. This issue will be resolved in Release 22.R3 (11.48).

SaaS 2022-May: Release 11.46.2

Bug Fixes

New User Experience

• PB-84695: We experienced increased processing times and a combination of Web UI errors, API errors and failed SSO login operations. This issue is now resolved.

• PB-84571: Fixed an issue in which exceptions caused by invalid SSO metadata were not managed properly. This created a performance issue in SSO.

• PB-81815: Fixed an issue in which changing a SAML setting in OneSpan Sign BackOffice necessitated a restart of the sso-service.

Signer Experience

• PB-84021, PB-84359: Fixed an issue in which signing via the Uanataca Trusted Service Provider was failing due to an internal error.

SaaS 2022-May: Release 11.46.1

What's New

Senders

• Prevent senders from permanently deleting transactions: Before this release, senders could permanently delete a transaction, no matter what its state (e.g., In Progress, Completed). A new setting in OneSpan Sign BackOffice enables Account Administrators to hide the Permanently Delete button in the sender part of the New User Experience. When that button is hidden, senders cannot permanently delete any transaction.

Bug Fixes

Signer Experience

• PB-83815: Fixed the following issue. When signed documents were viewed using the PDF Preview feature of Firefox or a Chromium-based browser, the browser might not correctly render certain components (e.g., a cross in a checkbox). We strongly recommend viewing signed documents with Adobe Reader/Acrobat Pro.

Known Issues

• PB-84021: Signing via the Uanataca Trusted Service Provider fails in the US1 Production environment. This failure has been traced to an internal error that occurs during data storage. That error will be fixed in an upcoming release.

SaaS 2022-Apr: Release 11.46

What's New

Senders

• Can create conditional logic on optional signatures: It is now possible to create conditional logic rules based on optional signatures. Specifically, when a sender creates a transaction, they can specify certain rules to be triggered when a signer signs an optional signature.
• Can set new rules for Checkbox Groups: Senders can now configure the following validation rules for a Checkbox Group: (1) At least (enforces a minimum number of boxes to be checked for the group); (2) At most (enforces a maximum number of boxes to be checked for the group); (3) Exactly (enforces an exact number of boxes to be checked for the group); (4) Range (enforces a minimum and maximum number of boxes to be checked for the group).
• Can download Evidence Summary & documents together: Senders can now download a transaction’s documents and its Evidence Summary together in a zipped file. Formerly, they had to download the Evidence Summary and documents separately.
• Can download Evidence Summary for incomplete transactions: Enabled the Evidence Summary to be downloaded from the sender part of the User Experience, even if the associated transaction is not completed. Note: This feature must be enabled per account, and is OFF by default. To activate it, please contact our Support Team.
• Better handling of large download files: Formerly, senders couldn’t receive an email with a completed transaction’s documents and/or Evidence Summary if the associated attachment was larger than 10 MB. If the attachment exceeds 10 MB, the sender now receives an email with a download link that will direct them to the relevant Transaction Details page. There, they can download the transaction’s documents and Evidence Summary in the usual way.
• Senders are warned of visibility issues: When a sender chooses a primary Branding color or an Alert color that has a low contrast ratio, the following warning message now appears: This color might cause visibility issues.

Signer Experience

• Can apply QES with Swisscom: Qualified electronic signatures (QES) can now be applied via Swisscom within the jurisdictions of eIDAS and ZertES. This integration with Swisscom: (1) on-boards new signers quickly and easily; (2) improves the User Experience when documents are signed with QES. Limitation: This feature is not yet available in all supported languages.

Developers

• SDK can add signature images: The SDK can now be used to add Image files as signatures in documents.
• Enabled new rules for Checkbox Groups: New validation rules for Checkbox Groups are described in the What's New > Senders section above. To successfully implement these rules, we needed an RHF library (react-hook-form.com). This in turn required us to change the syntax of our Field IDs. Field IDs are now “sanitized” by replacing all special characters with alphanumeric characters. Please take this into account if you are testing OneSpan Sign’s User Experience through an automated UI test framework such as Selenium (www.selenium.dev).

Virtual Room

• Host can extend a session indefinitely: The host can now extend a Virtual Room session any number of times. Before this release, a Virtual Room session could be extended only once.
• Host can close a session: The host can now close a Virtual Room session via an option in the More actions menu.
• Signers can review documents before a session: Signers can now review the documents associated with a Virtual Room transaction before a Virtual Room signing session. Specifically, signers can click a new Review button in the Virtual Room’s waiting room. Clicking it takes a signer to the documents, which can be reviewed but not yet signed. Once the host starts the Virtual Room session, the signers are admitted to the session, and documents can then be signed.
• Notifications sent when videos are downloadable: Added an API Event notification that is sent when a Virtual Room video recording is ready for download.
• Better mobile experience: We improved the mobile experience of Virtual Room sessions. Note: This is a work-in-progress that future releases will continue to improve.

Evidence Summary

• Can store a signer's geolocation: Enabled the system to gather a signer’s geolocation from their browser information, and store that geolocation in the Evidence Summary document. Note: (1) signers can configure their browser to block it from providing their geolocation; (2) this feature is enabled via a setting in OneSpan Sign BackOffice.

eOriginal

• Notification sent if an eDeposit fails: Customers are now notified if an attempt to eDeposit their documents in an eOriginal vault has failed.

• Cannot download authoritative copies: Users are now prevented from downloading authoritative copies of documents that will be deposited in eOriginal vaults. If they try to do so, they will end up downloading non-authoritative copies that are watermarked and flattened.

Bug Fixes

Signer Experience

• PB-80810: Fixed a Signer Experience issue in which Firefox 96 prevented signers from signing.
• PB-80838: Fixed the following issue. If radio buttons were added as required fields, a bug affected the Required Actions counter in the upper-right corner of the Signer Experience. In particular, selecting a radio button failed to increment the "completed actions" counter of the Required Actions widget (i.e., the "x" in "Required Actions x of y").
• PB-79623: Fixed an issue in which the system presented the Capture Signature dialog box to a signer multiple times, thus enabling them to apply different signatures in the same document. Instead, the system should have applied the signature it first captured to all the signer's Signature Boxes.
• PB-80806: Fixed an issue in which the system truncated the image of a captured signature if the signature had been captured on a mobile device; and the image was retrieved via an API call.
• PB-78788: Fixed an issue in which the user was getting a blank screen on their mobile device when they tried to access a transaction that required their Mobile Signature.
• PB-80811: Fixed an issue in which Signature Fields appeared in wrong places when documents were previewed in the Web UI via the "eye" icon.
• PB-82274: Fixed the following issue. When a signer had multiple Capture Signature fields in a document of an e-Notary transaction, an error occurred in the following situation. If the signer drew their signature in one of those Capture Signature fields, and then uploaded a signature image using the "Capture Signature from file" option, the system failed to place the drawn signature in all the signer’s Capture Signature fields.

Senders

• PB-78448: Fixed an issue in which a shared template could not be seen by anyone except the sender who created it.
• PB-76293: Fixed the following issue. After a sender deleted all transactions on the second page of listed transactions, they saw no transactions. Instead, the sender should still have seen the transactions on the first page.
• PB-80510: Fixed an issue that sometimes triggered an error when a conditional logic rule was being created for a transaction in which the Transaction Owner was also a signer.
• PB-78452: Fixed an issue that arose when the system imported fields from an accessible transaction’s PDF. The problem was that the names of fields in a drop-down list in the sender part of the User Experience had been changed from the fields' original names in the PDF.
• PB-78481: Fixed an issue in which special characters (e.g., apostrophes, double quotes) were rendered with a "Z0" prefix in the Field Import drop-down list when accessible transactions were being created.
• PB-78893: Fixed an issue in which the system failed to send email reminders that had been configured in a transaction template.
• PB-78169: Fixed an issue in which reminder emails were sent after a transaction was complete, but optional signatures had not been signed.

User Experience

• PB-78245: Fixed an issue in which the More actions menu was disabled for transactions, but subsequently appeared on user-authentication pages.
• PB-78166: Fixed incorrect Japanese translations of text in the product's Terms and Conditions.
• PB-78052: Fixed an issue in which the system presented a 403 error to a delegated user when they tried to view a delegated transaction.

Account Owners & Admins

• PB-79434: Fixed an issue that prevented groups from being created when sub-accounts were enabled.
• PB-61105: Fixed an issue in which the system threw an error when a user tried to create a group in a sub-account.
• PB-60392: Fixed an issue in which a sub-account user could not be deleted.
• PB-77955: Fixed an issue in which a 401 error appeared if a user requested an API token for a sender whose email address had the same suffix as the email address of another sender in the same account.

Developers

• PB-80323: Fixed the following issue. When a developer injected text fields in a PDF document, the JSON payload specified a font size for the injected fields. The problem was that the system failed to apply the specified font size to those fields.

Evidence Summary

• PB-79270: Fixed an issue in which the Evidence Summary failed to record a user’s remote signing of an in-person transaction.

Data Retention

• PB-79004: Fixed an issue in which transactions sometimes failed to expire on their configured expiry dates.

Accessibilty

• PB-75886: Fixed an accessibility issue in which Screen Readers read a banner about cookies every time they focused on a Close button or an OK, I agree button.

eOriginal

• PB-79122, PB-78928: Fixed an issue in which our Digital Mortgage or Digital Lending workflow failed to trigger the eDeposit of documents in an eOriginal vault.

Vulnerabilities

• PB-61589: Mitigated a vulnerability in which OneSpan Sign session cookies were set with a redundant "secure;" attribute.

• PB-72042: Mitigated a vulnerability in which multiple Oracle patches were missing. We applied the latest Oracle patches to the affected areas.

• PB-79609: Mitigated the CVE-2021-42575 vulnerability by upgrading the OWASP Java HTML Sanitizer library to version 20211018.2.

• PB-80502: Mitigated log4j vulnerabilities by upgrading each affected library to version 2.17.1 of the Log4j Core library.

• PB-79017: To remove vulnerabilities, we: (1) upgraded the libraries velocity-1.7.jar and jstl-1.2.jar; (2) removed the library plexus-utils-1.5.6.jar from the OneSpan Sign Application Backend.

Performance Improvements

• PB-75685: Improved the Signer Experience’s performance by disabling image rendering. Image rendering has not been needed since we deprecated the Classic Signer Experience.

• PB-79926: Improved the Signer Experience’s performance by improving Front End algorithms.

• PB-75902: Improved the User Experience's performance by implementing document-caching techniques.

Changed Behavior

• PB-79665: Changed the system’s Data Retention behavior so transactions are deleted the day after the date on which their retention is due to end.
• PB-77813: We modified the behavior of groups of radio buttons. Now if a radio button from a group is marked as required, the entire group is marked as required. These requirements are nonetheless satisfied when a single button from the group is selected.
• PB-78887: Changed the Evidence Summary's encoded hash for a Virtual Room video recording from a base-64-encoded hash to a plain-text MD5 hash. The latter is easier to decrypt.
• PB-78682: To ensure compliance with ADA standards (WCAG 2.1), we now warn senders when their chosen primary Branding color or Alert color has a low contrast ratio. Such warnings also enable senders to prevent the disappearance of UI components due to a color conflict (e.g., white alerts on a white background).
• MAIN-6598: When a signer session expires, in certain environments the signer used to be redirected to OneSpan Sign’s Login page. Now, in all environments the signer is redirected to an error page that states their session has expired.

Known Issues

• PB-84003: An issue arises in the following circumstances: (1) Senders A and B are members of the same sub-account; (2) Senders A and B are each other’s delegates; (3) Sender A creates a template in the sub-account. When Sender B is subsequently in the sub-account, and is acting as a delegate for Sender A, they should be able to see the new template. However, they can’t. A workaround is for Sender B to re-select the sub-account from the Accounts menu. They can then see the new template.
• PB-74520: Suppose an API user creates a transaction, and specifies the value '0' for the maxLength parameter on Text Fields. If a signer subsequently enters any amount of text into a Text Field, it will trigger the following error: The field's value is too long. This issue will be fixed in an upcoming release. Meanwhile, the workaround for API users is to exclude the maxLength parameter from the payload. This issue does not affect SDK users.
• PB-80669: Sometimes an account owner with the User Management permission cannot delete other users from their account. Recent code changes mean that deleting other users now requires both the User Management permission and the Roles permission. A sufficient workaround is to assign the account owner the Admin role (via OneSpan Sign BackOffice).
• PB-82567: Giving a group of checkboxes and a group of radio buttons the same name causes errors in the Signer Experience. The workaround is to ensure that these different kinds of groups have different names.
• PB-82023: Windows Explorer is the default file-compression application for versions 10 and 11 of Microsoft Windows. A bug or limitation in Windows Explorer is preventing users from viewing the content of the EslTransactionsPIIReport file created by the Schedule Reports feature of OneSpan Sign BackOffice. This problem can easily be mitigated by using a third-party file-compression application such as 7zip or winrar.
• PB-82852: When trying to create an accessible transaction, an "HTTP 400 Bad Request" error occurs if the parameters Stop Image Rendering and Extract Text Tags are both enabled in OneSpan Sign BackOffice. This issue will be fixed in an upcoming release.
• PB-83384: When trying to confirm signed documents (accessible or not), the Confirm button sometimes fails to respond when it's clicked. This occurs only if the name in one of the documents' Signature Fields contains a period (.). The functionality of the Confirm button can easily be restored by refreshing the browser.
• PB-83688: This issue arises when a signer repeatedly fails to authenticate themselves via ID Verification, and is locked out of a transaction. When the sender subsequently views that signer’s status in the User Experience, they should see a “locked signer” icon. The sender can then interact with that icon to unlock the signer, and resend the transaction. The problem is that the icon is not appearing, so the signer cannot be unlocked.
• PB-83742: Signing a document on Windows 11 via PCC with a soft certificate sometimes causes a Personal Certificate Client Error. The document cannot be signed because the certificate selected for this purpose is invalid. If this happens, please select a different certificate and try again.
• PB-83815: When signed documents are viewed using the PDF Preview feature of Firefox or a Chromium-based browser, the browser may fail to correctly render certain components (e.g., a cross in a checkbox). If this happens, please view the document using Adobe Reader/Acrobat Pro.
• PB-84199: An issue arises when the Signature Navigator has been configured to iterate through a document’s checkboxes. The problem is that it skips over checkboxes if they are in a Checkbox Group.
• PB-84341: If a signer has been assigned the SMS authentication method, using a Safari v13 browser with iOS 13 crashes the signing process. The error message that appears is Unhandled Server Error. As a workaround, signers can do any of the following: (1) use a different browser; (2) upgrade to a higher version of Safari; (3) upgrade to a higher version of iOS.
• PB-84954: An issue arises in the following circumstances: (1)a template is created with multiple signers, one of whom is assigned Conditional Fields; (2) a transaction is created from the template, and the signer with the Conditional Fields is removed; (3) the transaction is distributed for signing; (4) a signer completes their portion, and clicks Confirm. At this point, an error message appears. This issue will be fixed in an upcoming release. Meanwhile, the workaround is to: (1) manually delete the relevant document from the transaction; (2) add the document to the transaction again; (3) redistribute the transaction for signing.

SaaS 2022-Jan: Release 11.45.3

Bug Fixes

• PB-80515: Fixed an issue that prevented signers from signing a transaction with an iPad or iPhone. When a signer tried to access the Signer Experience, the document would not load. This in turn caused the browser to continuously refresh itself until an error was thrown.
• PB-80810: Fixed an issue in which the Designer would not load in an iFrame when Firefox v96 was being used.

Known Issues

• PB-80838: If radio buttons have been added as required fields, a bug affects the Required Actions counter in the upper-right corner of the Signer Experience. In particular, selecting a radio button fails to increment the "completed actions" counter of the Required Actions widget (i.e., the "x" in "Required Actions x of y").

SaaS 2021-Dec: Release 11.45.2

Bug Fixes

• PB-80033: Fixed an issue in which users couldn't access a shared template in a sub-account.

Vulnerabilities

• PB-80115: Recently the Apache foundation announced a number of security vulnerabilities (CVE-2021-44228 and CVE-2021-45046) in the Log4j2 library for Java applications, affecting all versions from 2.0-beta-9 to 2.15.0. In order to mitigate these vulnerabilities, we have upgraded the affected libraries to Log4j Core library version 2.16.0. This version of the library mitigates the remote code execution and denial-of-service attacks that could result from the vulnerabilities, and is the latest version provided by Apache.

SaaS 2021-Dec: Release 11.45.1

Bug Fixes

• PB-78695: Fixed a Signer Experience performance issue that was causing a noticeable delay in the system's response to the signer's selection of a radio button or checkbox. This gave signers the impression that they had not successfully made a selection. This release has greatly improved the system's response time to the selection of a radio button or checkbox.
• PB-79716: Fixed an issue in which transaction documents could not be opened if a user tried to sign using the Mobile Capture method.

Known Issues

• PB-77405: Disabling a Checkbox Group does not clear a checkbox if it has already been selected. This could occur as follows: (1) conditional logic is configured to disable a Checkbox Group if the signer interacts with a different field (e.g., a text field); (2) the signer selects a checkbox in the group: (3) the signer then interacts with the different field that triggers the conditional logic; (4) that logic disables the Checkbox Group. In this situation, the value entered for the checkbox will persist, even though its group is supposed to be disabled.
• PB-77381: The Action Progress Bar in the Signer Experience may not accurately reflect the number of actions a signer has left to complete. For example, the progress bar may read Required Actions 0 of 2, when it should read Required Actions 0 of 3. Such errors can arise when conditional logic is applied to the first item in a group of checkboxes or radio buttons.

SaaS 2021-Dec: Release 11.45

What's New

Signing Ceremony

• More user-friendly Cookie Policy: Signers who have accepted the Cookie Policy once will no longer be prompted to accept that policy when they access the Signing Ceremony again. Note: (1) the Cookie Policy Consent Agreement is browser-specific; (2) a prompt to accept the Cookie Policy will reappear if the signer clears their browser cache, or if they access their browser window in Incognito/Private mode.

Virtual Room

• Delegates can host meetings: Delegates can now act as the host of a Virtual Room meeting.
• Hosts can see attachment numbers: During a Virtual Room meeting, the host can now see how many attachments the sender asked each recipient to upload.
• Senders reminded that videos will be deleted: Email notifications will now be sent to the sender of a completed Virtual Room transaction to remind them that the transaction’s Video Recordings will soon be deleted. These reminders will be sent: (1) three days before the recordings are deleted; (2) one day before the recordings are deleted.

In-App Reporting

• Reports have more ID Verification info: Transaction Reports now contain more information about transactions that have ID Verification enabled. For each ID Verification attempt in a transaction, the reports now record: (1) if the attempt was for Document Verification Only or Document Verification with Facial Comparison; (2) if the attempt succeeded or failed ; (3) the signer's unique identification number (signer uid).

Developers

• SDKs can manage Checkbox Groups: SDKs can now be used to manage (e.g., create, update) Checkbox Groups.

Bug Fixes

Signing Ceremony

Accessibility

• PB-76252: Fixed an accessibility issue in which the NVDA Screen Reader failed to read the Enable accessibility mode button when signers tabbed to it.

• PB-76623: Fixed the following issue. After using the keyboard’s arrow keys to navigate to the Next button on the Reassign Recipient screen, the NVDA Screen Reader read the text for two buttons (Next and Cancel).

• PB-76625: Fixed the following issue. After using the keyboard’s arrow keys to navigate to a single button on the Signature Capture screen, the NVDA Screen Reader read the text for all that panel's buttons (Clear, Cancel and Done).

• PB-77993: Fixed an issue in which an Unhandled Server Error occurred when a signer switched to Accessibility Mode.

In-Person Transactions

• PB-77012: Fixed an issue in which the Enter key became disabled after an incorrect SMS passcode was entered for an in-person transaction.
• PB-77018: Fixed an issue in which the Signer Locked Out page failed to appear after a signer repeatedly failed SMS authentication in an in-person transaction.

Other

• PB-77728: Fixed an issue in which a document could not be accessed if it had a Checkbox Group whose name contained a period.
• PB-77173: Fixed the following issue, which occurred when the Overview page was enabled. After External Signer Verification was successful, the system presented an unexpected signing flow.
• PB-76567: Fixed the following issue. If a signer dismissed an error banner on a document during a Virtual Room session, the system automatically scrolled to the top of the document.
• PB-76013: Fixed the following issue. If OFAC Blacklist was enabled on a sub-account, an error was thrown when a signer tried to access a transaction created in that sub-account.
• PB-76086: Fixed the following issue. When a delegate tried to capture their signature from a file, the system failed to properly process their registered signature image.
• PB-76670: Fixed an issue in which the feedback bar failed to minimize to the top bar when the signer scrolled down to other pages of a document. This occurred when the New Signer Experience was accessed within an iFrame from a mobile device.
• PB-76690: Fixed an issue in which the feedback bar displayed incorrect information when the BackOffice settings for the relevant account: (1) enabled conditional fields; (2) configured the Signature Navigator to iterate through all the fields in a document (both required and optional).
• PB-76830: Fixed an issue in which the signature button’s background color was changed to white, but the button’s font color did not respond to this change. The font color remained white, so the button’s caption became invisible.
• PB-77359: Fixed an issue in which characters entered in very small Text Fields or Text Areas failed to appear in the New Signer Experience. Note: This problem has never occurred in the Classic Signing Ceremony.
• PB-78194: Fixed the following issue. Signatures associated with an auto-field (e.g., signing date) were applied within a document. The problem was that these signatures were rendered invalid by the subsequent application of a Capture Signature in the document.
• PB-77810: Fixed an issue in which the Signing Ceremony failed to reflect a label field’s specified font size.

Senders

Designer

• PB-77843: Fixed an issue in which the following error message appeared when a sender tried to delete documents from the Designer: Something went wrong and your request could not be completed. Please try again.
• PB-77069: Fixed an issue in which some uploaded PDF files could not be viewed in the Designer from a Chrome browser.

Other

• PB-76530: Fixed an issue in which the Success message was displayed for a Bulk Sending operation, but the system failed to process the sent transactions.
• PB-77639: Fixed the following issue, which occurred when an account’s Roles and Permissions feature was enabled. A sender's permissions were by-passed when they created a transaction. This occurred because the system validated the sender's access only by checking their user type, which was Manager.
• PB-73499: Fixed an issue in which the system seemed unable to apply a layout to a transaction.
• PB-72456: Fixed the following issue, which occurred when a transaction required the sender’s signature. The Info icon failed to appear next to the transaction in the Dashboard's Recent Transactions list.
• PB-74349: Fixed the following issue. When a Transaction Owner previewed a document that was part of a transaction in the state SENT, a Document View callback notification was wrongly triggered, and a Document View audit event was wrongly logged.
• PB-75294: Fixed an issue in which the Preview panel in the sender part of the New User Experience failed to display a logo that a sub-account had inherited from its parent account.
• PB-77194: Fixed some Japanese translations that confused senders who were trying to create or manage transactions.

Developers

• PB-76585: Fixed an issue in which the system failed to replace the variable $PACKAGE_OWNER_NAME with the name of the Transaction Owner in the Bulk Send Completed email (email.bulk.send.completed).

• PB-77900: Fixed an issue in which the API was used to create a template with the same name as an existing template.

• PB-64815: Fixed an issue in which customers were able to send our system an incorrect AccountUID via the API.

Account Owners & Admins

• PB-77560: Fixed the following issue. After an account was canceled, the system failed to delete the associated CMK (Customer Master Key).

• PB-77745: Fixed an issue in which SSO auto-provisioning would not work if the user attributes accountid and role were not specified.

Virtual Room

• PB-77875: Fixed an issue in which the system failed to create a Video Recording file for a Virtual Room meeting if the meeting being recorded timed out.

In-App Reporting

• PB-76524: Fixed an issue in which a user with the Reports permission could not access Transaction Reports or Account Reports about their account.

Changed Behavior

• PB-77005: It is no longer possible to save layouts that have masked fields.

• PB-77808: The new buttons Review, Sign and Join may now appear on the Transaction Details page for Virtual Room transactions. Clicking the Review button takes a reviewer to the transaction’s Signing Ceremony. Clicking the Sign button takes a signer to the transaction’s Signing Ceremony. Clicking the Join button takes the user to a Welcome page that provides an overview of the transaction.

Known Issues

• PB-78762: When a “Make required” or “Make optional” condition has been configured for a Signature Field in a document, and that condition changes after a different signer has confirmed the same document, there is an issue with that Signature Field in the resultant PDF.

• PB-79423: When a signer has enabled accessibility mode, and then views a document, some of the document’s fields (e.g., text boxes, checkboxes) may extend beyond the document’s right edge.

• PB-79517: When senders view the Field Settings panel, they cannot see all of a checkbox’s settings at once if their computer’s display has been scaled to more than 125%. Until this issue is fixed, the workaround is to zoom out.

• PB-82274: When a signer has multiple Capture Signature fields in a document of an e-Notary transaction, an error occurs in the following situation. If the signer draws their signature in one of those Capture Signature fields, and then uploads a signature image using the "Capture Signature from file" option, the system will fail to place the drawn signature in all the signer’s Capture Signature fields. This issue will be fixed in OneSpan Sign 11.46.

SaaS 2021-Oct: Release 11.44

What's New

Virtual Room

• Added video recording: Video recording is now possible for Virtual Room transactions. Note: (1) Video recording is available only for Virtual Room transactions, and must be turned on for an account. To turn the feature on, please contact a Sales representative. (2) The transaction host can turn the recording on and off during signing sessions. If a recording is paused and then resumed during a single session, a single video will be created at the end. If there are multiple signing sessions, multiple videos will be created for the transaction. (3) Processing of the videos is done after the transaction is completed, and may take up to an hour. The recordings will be available on the Transaction Details page in the sender part of the New User Experience. (4) Each video will consist of composed audio and video tracks of all participants. (5) Recordings will be deleted seven days after their creation, so senders must download and store the recordings before then.
• Added info in the Evidence Summary: If a transaction is a Virtual Room transaction, the Evidence Summary document now: (1) shows the Transaction Type; (2) stores Virtual Room actions.

Enterprise Administration

• Sub-account actions for API users: An API user with suitable account and user permissions can now: (1) retrieve a given user’s roles in one or more sub-accounts; (2) assign one or more roles in a sub-account to a given user. Both these API procedures require the following prerequisites: (1) sub-accounts must be enabled for the account via BackOffice; (2) the API user must have access to the API via their own API key; (3) the API user must have the User-Management permission on the sub-account.

User Authentication

• Support for a second authentication method: Formerly, if ID Verification was assigned to a recipient, another authentication method could not be assigned to that recipient at the same time. Starting with this release, ID Verification and KBA Authentication can both be assigned to a recipient. To access the relevant transaction, the recipient must pass both authentication methods.
• Display of remaining ID Verification attempts: Each non-final time that a recipient tries and fails to authenticate themselves via ID Verification in order to access a transaction, a screen now shows them the number of remaining permitted authentication attempts they have.

Signing Ceremony

• Added support for Arabic: Added support for the Arabic language in the New Signer Experience. This includes support for right-to-left word wrapping in Text Area fields. Arabic is not yet supported in the sender part of the New User Experience. Known issues: (1) watermarks in Arabic are not yet fully working; (2) new lines entered in Text Area fields appear as a "?" in the Evidence Summary document.
• Improved accessibility flow: Enhanced accessibility flow by ensuring that navigation to a subsequent document takes the signer directly to the document instead of to the top menu.
• Improved document accessibility: A Go to document shortcut is now available for all transactions (accessible and non-accessible). It redirects users to the transaction's main document.

Senders

• Added support for groups of checkboxes: Senders can now create a group of checkboxes. If the sender sets any checkbox in a group as required, then during signing the signer must select at least one member of the group. Note: (1) Conditional logic on a group of checkboxes is not supported. (2) SDK support is not yet available. It will be added in a future release. (3) Extraction is not yet available. It will be added in a future release. (4) This feature is not yet 100% ADA compliant. This will be added in a future release. (5) Periods (".") are not currently supported in Checkbox Group names. This issue will be resolved in a future release.
• Full display of long messages: The window on the Transaction Details page that contains the message sent to recipients now expands if the message exceeds that window's default size. This ensures that senders can see the entire message.

Bug Fixes

Signing Ceremony

In-Person Transactions

• PB-75437: Fixed an in-person transaction issue in which a subsequent signer's Capture Signature was not reset after the signer clicked Undo, and tried to sign again.
• PB-70667: Fixed an issue in which an in-person transaction host who was not the Transaction Owner could access the Transaction Edit page after the transaction was declined. Now for such hosts: (1) the Done button is hidden on the Transaction Declined page; (2) they must select Exit Signing to exit the Signing Ceremony, at which point they are redirected to the Dashboard.
• PB-76187: Fixed an issue in which the Transaction Owner couldn’t access the in-person Thank You page when auto-redirect was enabled for the Handover URL.
• PB-76795: Fixed an issue in which the SMS verification prompt failed to appear to a signer in an in-person transaction when the Second In-Person Affidavit was disabled.

Accessibility

• PB-70964: Fixed an accessibility issue in which Screen Readers failed to automatically read the Cookie Policy screen.
• PB-58816: Fixed an accessibility issue in which multiple tabs were required to reach the hidden Enable accessibility option. That option is now available right after the Cookie Policy screen.
• PB-65060: Fixed an accessibility issue in which, upon signing a Signature Block, the Screen Reader mistakenly read the word Unavailable.
• PB-75200: Fixed an accessibility issue in which there were two H1 headings on the Summary Complete page.
• PB-72644: Fixed an accessibility issue in which Screen Readers failed to vocalize the correct total number of uploads for a Virtual Room transaction when the host expanded the Uploads list.

Conditional Fields

• PB-76935: Fixed an issue in which transactions using Conditional Fields on radio buttons or checkboxes failed to show the correct transaction status in the Required Actions feedback bar.
• PB-76573: Fixed an issue in which radio buttons and checkboxes in a document with Conditional Fields failed to appear as selected until the document was refreshed.
• PB-76663: Fixed a performance issue that was triggered when documents with Conditional Fields were confirmed.

Other

• PB-76845: Fixed an issue in which selecting or clearing a checkbox didn't work properly in certain scenarios.
• PB-76834: Fixed an issue in which the document status was not properly updated in the Documents pane.
• PB-76455: Fixed an issue in which the Summary Complete page was displayed to a signer in a transaction that was assigned to a group, though it was not yet that signer's turn to sign.
• PB-75628: Fixed an issue in which the Reassign Recipient option (also known as Change Signer) was still present for Declined transactions.
• PB-76354: Fixed the following issue. If Enforce Capture Signature was enabled, a hand-drawn signature was not reset after undoing the signature.
• PB-76087: Fixed the following issue. A sender accessed a transaction for which they were not the Transaction Owner, and they declined to sign. The Transaction Declined screen appeared, on which the user clicked More Actions > Exit Signing Mode. The user should then have exited Signing Mode with no error messages, but an error message did appear. When the user closed the error message, they landed on an Access Denied page with no navigation options. The fix lets such users exit Signing Mode without an error message, and redirects them to the Dashboard.

Senders

Designer Page

• PB-75242: Fixed an issue in which senders couldn’t go to the Designer page after they created a transaction from a shared template that had been created by another sender.
• PB-76282: Fixed an issue in which senders could go to the Designer page when the relevant transaction had been created without a document via the API.
• PB-72709: Fixed a Designer page issue in which certain conditions led to a failure to save the Is Required flag's value for Form Fields.

Other

• PB-70909: Fixed the following issue. When users click the CANCELLED part of the Dashboard's pie chart, they should be redirected to view recent Declined transactions. Instead, they were redirected to view the status of trashed transactions.
• PB-74870: Fixed an issue in which the Cookie Policy screen prevented senders from creating a handwritten signature on the Signature page (among the My Account set of pages).
• PB-75387: Fixed an accessibility issue in which the aria-label attributes for radio buttons and checkboxes had unexpected values.
• PB-76375: Fixed an issue in which Japanese translations for Access Delegation were not intuitive.

Account Owners & Admins

Accessibility

• PB-75982: Fixed an accessibility issue in which the NVDA Screen Reader did not properly read a Close button.
• PB-75918: Fixed an accessibility issue in which the NVDA Reader did not completely read several links.
• PB-76095: Fixed the following accessibility issue. When a user navigated to the Reports link using the arrow keys, the NVDA Screen Reader should have read just the Reports link. Instead it read the Reports link and the Admin link.

Other

• PB-74985: Fixed an issue in which a 504 Gateway Time-out error occurred while trying to enable sub-accounts.

Developers

• PB-64787: Fixed an issue by ensuring that when the Roles and Permissions feature is enabled, only users with the Data management self-service permission can access our Data Retention feature via the API.

Changed Behavior

• PB-74060: To improve accessibility, we converted the Exit Signing Mode pop-up window for senders into a notification that appears in the top bar of the New Signer Experience.

Known Issues

• PB-77728: Periods (".") are not currently supported in Radio Group names or Checkbox Group names. This issue will be resolved in a future release.

• PB-77822: A signer is auto-redirected to the Handover URL if the auto-redirect option is enabled, and the New Signer Experience is accessed from the sender interface. This should not happen for regular transactions. This issue will be resolved in a future release.

• PB-78102: This issue arises when the API is used to add to a document: (1) a Checkbox Group; (2) other checkboxes for which validation rules have not been configured ("validation":null). If this happens, an error will appear when the recipients try to access the transaction in the New Signer Experience. This issue will be resolved in a future release.

• PB-78194: This issue arises when signatures associated with an auto-field (e.g., signing date) are applied within a document. The problem is that these signatures are rendered invalid by the subsequent application of a Capture Signature in the document.

• PB-78448: When a template is being created, the Share template toggle switch is not working properly. If clicked, the status is not saved visually. Nonetheless, the template is shared with other senders on the account. This issue will be resolved in a future release.
• PB-77810: The Signing Ceremony is failing to reflect a label field’s specified font size. Instead, the field's text appears with the field's default font size. This issue will be resolved in the next release.

• PB-78762: When a “Make required” or “Make optional” condition has been configured for a Signature Field in a document, and that condition changes after a different signer has confirmed the same document, there is an issue with that Signature Field in the resultant PDF.

SaaS 2021-Sep: Release 11.43.2

Bug Fixes

New User Experience

• PB-77545: Fixed an issue in which documents failed to load in the Designer and in the New Signer Experience if the user’s browser was Safari 12.x.

SaaS 2021-Sep: Release 11.43.1

Bug Fixes

Signing Ceremony

• PB-77019: Fixed an issue in which recipients couldn’t access a transaction from an email link.

• PB-76908: Fixed an issue in which the tops of Japanese characters were cut off in multi-line Text Area fields.

Senders

• PB-76961: Fixed an issue in which senders couldn’t access the full list of groups.

SaaS 2021-Aug: Release 11.43

What's New

ID Verification

• Introducing ID Verification: This release introduces the following new methods of authenticating a recipient's identity: (1) Document Verification Only validates the recipient's driver’s license, passport, or national identity card; (2) Document Verification with Facial Comparison examines one of those identity documents, and compares the recipient's photo on that document with the recipient's selfie. Collectively, these two methods are called ID Verification. To enable and configure ID Verification for your account, contact your Account Representative. Note: ID Verfication for OneSpan Sign is available only in the following environments: US1, US2 , CA and EU. It is not available in the US FedRAMP or AU environments.

New User Experience

• Guidance on Fonts: New documentation tells users how to avoid problems with the fonts in documents that are created or uploaded for use in transactions — see Supported Fonts.

Signing Ceremony

• Can sign via Uanataca without cookies: Signing via the Uanataca Trusted Service Provider no longer uses cookies to store session information. This complements similar Signing Ceremony functionality introduced in OneSpan Sign 11.42 and 11.38. Nonetheless, scenarios that have integration points with third-party entities such as Equifax or an IdP server may require the use of cookies — such requirements are beyond our control.
• Bottom bar on Uploads page: As of this release, the informative bottom bar on the Uploads page will always appear if there are optional and/or required attachments to be uploaded by the signer.
• Removed Sudan from OFAC list: Removed Sudan from the OFAC list, since OFAC no longer lists Sudan as an embargoed country.

Senders

• Renamed transaction types: When a sender creates or edits a transaction or template in the New User Experience, the drop-down menu of transaction or template types now lists the following renamed options: (1) eSigning (a normal signing transaction that isn't an in-person, notarization or Virtual Room transaction); (2) In-Person eSigning; (3) In-Person Electronic Notarization ceremony (formerly called Notarization); (4) Virtual Room.
• Virtual Room details on Transaction Details page: Virtual Room information now appears on the Transaction Details page of a Virtual Room transaction.
• Can mask fields in the Virtual Room: Selected fields in a Virtual Room transaction can now be masked. When a sender adds a field to a document, they can slide its Mask field toggle switch to ON. If that has been done, during the Signing Ceremony that field will be visible only to: (1) the signer to whom the field is assigned; (2) the host.
• Improved import of accessible documents: When a sender uses the New User Experience to import an accessible document, a radio-button group in the document will now be imported as an entire group (not as particular radio buttons).
• Can send one transaction for all languages: When a document needs to be signed by signers who speak different supported languages, the sender can now send a single transaction to all the signers. The sender no longer needs to create a separate transaction for each language. A signed document will properly display the signers' Inputs in all the languages they used (regardless of the language specified for the transaction).

Developers

• New Callback Notification for SDKs: SDKs can now be used to configure a Callback Notification called Document Viewed. This notification is triggered when a signer views a document.
• New Event Notification: Created a JavaScript Event Notification that is triggered when the signer in an in-person or e-Notary transaction clicks the Done button on their Thank You page. Note: The signer Id is appended to the event: ESL:MESSAGE:SUCCESS:SIGNER_DONE:<signer id>
• Improved Costa Rican signatures: Documents that are signed with a Costa Rican timestamp are now PAdES BL-T LTV enabled. This empowers them to pass the Banco Central de Costa Rica's validation tool (Central Directo portal).
• SDKs can retrieve sub-account API keys in one call: Release 11.42 enabled a user to retrieve the API keys from all their sub-accounts via a single REST API call. This functionality is now available through the Java and .NET SDKs.

In-App Reporting

• Added a loading spinner: A loading spinner now appears while users are waiting for the system to finish downloading reports.

Bug Fixes

Signing Ceremony

In-Person Transactions

• PB-75491: Fixed an issue in which the hand-off between signers in an in-person transaction failed because the recipient had been assigned an unsupported language code.
• PB-74075: Fixed an issue that arose when an external signer accessed an in-person transaction using their Signer Authentication Token. In this case, the Completion Summary page failed to appear when the signer finished signing.
• PB-74140: Fixed an issue that arose when an in-person transaction was accessed using the Signer Authentication Token of a signer who could not host the session. For this signer, the Exit Signing option should not be available under the More Actions menu, but it was.
• PB-74686: Fixed an issue that arose in in-person and e-Notary transactions. When a signer completes and exits signing, they should see the signer's Thank You page. However, the system failed to display it for these transactions.
• PB-75247: Fixed an issue in which the host's Thank You page in an in-person transaction was missing the Download Documents button.
• PB-74695: Fixed an issue in which an in-person transaction's Thank You page for the host failed to appear after all signers had completed signing . This happened when the transaction had been configured to be completed manually, and so was not yet complete.

Accessibility

• PB-75409: Fixed an issue in which pre-filled text in a PDF's multi-line Text Field did not display properly in accessibility mode.
• PB-72717: Fixed an accessibility issue in which certain Screen Reader instructions were not clear enough. Those instructions described how to use a mobile device to apply a Capture Signature.
• Fixed multiple accessibility issues, mostly related to Screen Readers' failing to correctly read labels and other elements.

User Authentication

• PB-75220: Fixed an issue that arose when a recipient typed a correct code for SMS Authentication or a correct answer for Q&A Authentication, and then pressed Enter. At that point, the system should have let the recipient into the associated transaction, but it didn't.
• PB-70833: Fixed an issue in which a loading spinner continued to appear on a recipient's authentication page after the page was fully loaded.

Language

• PB-75563: Fixed an issue in which variations in the language code for a supported language caused an error when users tried to access the New Signer Experience.
• PB-74062: Corrected some translations into Japanese.

Other

• PB-75957: Fixed an issue in which PDF documents that did not have embedded fonts would not render correctly in the Signing Ceremony. For more information, see Supported Fonts.
• PB-75199: Fixed an issue in which signers experienced a lag when they tried to update a document's fields.
• PB-75136: Fixed an issue in which a OneSpan Sign BackOffice setting failed to work. That setting should have prevented a signing progress bar from appearing during the Signing Ceremony, but it didn't.
• PB-75565: Fixed an issue in which a signer couldn't access a transaction from an email link after the sender rejected one of the signer's attachments for that transaction.
• PB-75132: Fixe